Trying to move a client’s website from AWS to Netlify. Changed the nameservers from the default Route53 ones to that of Netlify. Whatsmydns.com shows that the nameservers have propagated successfully:
However, running an A record lookup on the same domain shows the IP of the old server and it opens the old website, not the one on Netlify:
How could this be happening? What’s the possible fix? I have no prior knowledge of AWS and Route53.
Hi @pexeixv
How long ago did you change the nameserver? I can see in the first screenshot at least one server where the new records have not propagated. Propagation takes time
If you are having issues, please provide the name of your Netlify site and the custom domain you are trying to connect to it.
Just did the change an hour ago.
The details:
I ran dig +trace tabnationcoding.com and it spitted out this this.
Particularly, these 5 lines indicate that it is getting the A record before the NS records, so it’s directly routing to 54.231.196.53
tabnationcoding.com. 5 IN A 54.231.196.53
tabnationcoding.com. 60 IN NS dns1.p06.nsone.net.
tabnationcoding.com. 60 IN NS dns2.p06.nsone.net.
tabnationcoding.com. 60 IN NS dns3.p06.nsone.net.
tabnationcoding.com. 60 IN NS dns4.p06.nsone.net.
In the Netlify Domains section of the UI, under tabnationcoding.com are there two NETLIFY records (one for tabnationcoding.com and one for www.tabnationcoding.com)?
SOA
% dig tabnationcoding.com SOA +noall +answer
; <<>> DiG 9.10.6 <<>> tabnationcoding.com SOA +noall +answer
;; global options: +cmd
tabnationcoding.com. 60 IN SOA ns-479.awsdns-59.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
vs NS
% dig tabnationcoding.com NS +noall +answer
; <<>> DiG 9.10.6 <<>> tabnationcoding.com NS +noall +answer
;; global options: +cmd
tabnationcoding.com. 60 IN NS dns3.p06.nsone.net.
tabnationcoding.com. 60 IN NS dns4.p06.nsone.net.
tabnationcoding.com. 60 IN NS dns1.p06.nsone.net.
tabnationcoding.com. 60 IN NS dns2.p06.nsone.net.
Thinking this might help