Nameservers updated but A record still points to old server

Trying to move a client’s website from AWS to Netlify. Changed the nameservers from the default Route53 ones to that of Netlify. 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 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	5	IN	A	60	IN	NS	60	IN	NS	60	IN	NS	60	IN	NS

In the Netlify Domains section of the UI, under are there two NETLIFY records (one for and one for


% dig SOA +noall +answer

; <<>> DiG 9.10.6 <<>> SOA +noall +answer
;; global options: +cmd	60	IN	SOA 1 7200 900 1209600 86400

vs NS

% dig NS +noall +answer

; <<>> DiG 9.10.6 <<>> NS +noall +answer
;; global options: +cmd	60	IN	NS	60	IN	NS	60	IN	NS	60	IN	NS

Thinking this might help