I am trying to migrate my domain from AWS Route53 to DO. I created the domain on DO and all the A records that are in Route53. Also added one new A record on DO as a test A record.

I updated the NS servers on Route53 to be the DO NS servers. ns1.digitalocean.com.
ns2.digitalocean.com.
ns3.digitalocean.com.

When I do a whois on this domain, I still am getting AWS NS servers. In some nslookup sites, it does show up as DO. Being in this limbo state is very unsettling. Is this just an inherently broken process of the Internet or is there a way I can remedy this so that the Internet converges on the DO NS servers? I’m hoping I missed a step somewhere. I did notice that the Route53 domain has a SOA record… does this need to be changed too?

1 comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
2 answers

Hi there @jmartine1026,

As it has been over a week already, it is mostlikely not really due to DNS caching.

As when you do a whois and you still see the old nameservers, this will mean that you need to do is go to your Domain name registrar (the company that you registered your domain name with) and change your Nameservers there. That will basically ‘tell’ your domain name which DNS zome it should use.

Let me know how it goes!

Regards,
Bobby

Normally all those things may take some time,but if your problem still not solve then try to contact with your domain provider they will surely help you and fix your problem.

Submit an Answer