We’d like to move our DNS over to AWS Route53 but instead of doing a full transfer, pointing the nameservers to AWS.
After setting the NS records for the domain, it seems like it hasn’t yet propagated. My experience has been that DNS changes typically take a couple of minutes, unless I’ve made a mistake somewhere (albeit often it’s said that it can take between 24-48 hours).
After running some dig commands, it seems like the NS records are still pointing to digital ocean.
Should I have made additional changes to get this to work?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
DNS changes within a zone such as what IP address an A record points to can be done very quickly in some cases. If the TTL (time to live) is set low as it is on DigitalOcean these types of changes can happen nearly instantaneously. Changing the nameservers associated with a domain with your registrar on the other hand can take up to a couple days depending on the registrar.
Note that changing the NS records within your zone will not change which nameservers your domain itself is pointed to. You need to make this type of change with your registrar (where you bought your domain) directly.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.