Page 1 of 1

Missing WWW A Record not allowing Let's Encrypt

Posted: Tue Nov 17, 2020 11:22 pm
by jashimili
Hi guys i just recently moved one domain to new server and technically it should be that i did everything correct but for some reason it's not working.

Upon checking intodns i get an error

Code: Select all

WWW A Record
ERROR: I could not get any A records for www.mydomain.com
And in the end i figured out this is preventing me from actually being able to use Let's Encrypt SSL because i get an error of missing www record.

These are the steps i did.

In my domain name provider i setup ns and ip

Code: Select all

ns1.mydomain.com 10.1.1.1
ns2.mydomain.com 10.1.1.1
In VestaCP i created the domain name under Web tab, under aliases is www.mydomain.com

In DNS settings, it's automatically created but i checked and there are all dns records it doesn't seem that anything is missing.

Code: Select all

$TTL 14400
@    IN    SOA    ns1.mydomain.com.    root.mydomain.com. (
                                            2020111731
                                            7200
                                            3600
                                            1209600
                                            180 )

@	14400	IN	NS		ns1.mydomain.com.
@	14400	IN	NS		ns2.mydomain.com.
@	14400	IN	A		10.1.1.1
ns1	14400	IN	A		10.1.1.1
ns2	14400	IN	A		10.1.1.1
www	14400	IN	A		10.1.1.1
ftp	14400	IN	A		10.1.1.1
mail	14400	IN	A		10.1.1.1
smtp	14400	IN	A		10.1.1.1
pop	14400	IN	A		10.1.1.1
imap	14400	IN	A		10.1.1.1
@	14400	IN	MX	10	mail.mydomain.com.
@	14400	IN	TXT		"v=spf1 a mx ip4:10.1.1.1 ~all"
_dmarc	14400	IN	TXT		"v=DMARC1; p=none"


It doesn't seem that anything is wrong and yet intodns is reporting www a record is missing, also i can't enable let'sencrypt

Re: Missing WWW A Record not allowing Let's Encrypt

Posted: Wed Nov 18, 2020 1:31 am
by grayfolk
May be few more time required for DNS updates (up to 48 hours). Try again in a few hours.

Re: Missing WWW A Record not allowing Let's Encrypt

Posted: Wed Nov 18, 2020 8:59 pm
by jashimili
Well the www a record i found the cause of the problem, it was actually for some reason controlled by domain name provider, i sorted that out but the problem with let's encrypt still exists so i guess it was not this what is causing the problem, i looked throughout the forum and none of the solutions works. I guess i will open a new topic and post some hosting details maybe something will come up as a solution.