To change nameservers safely, identify current DNS, back up the full zone, recreate required records at the new DNS provider, check website and email records, review DNSSEC, then update nameservers at the registrar and monitor propagation. Do not change nameservers before the new DNS provider has the correct records.
Who This Guide Is For This guide is for: · Domain owners changing DNS providers · Users connecting a domain to hosting or website builders · Businesses protecting email continuity · Agencies and resellers managing client DNS · Users transferring domains and replacing old registrar DNS
Before You Start Before you start, prepare: · Old nameservers · New nameservers · Full DNS backup · New DNS provider access · Website and email provider instructions · DNSSEC status · Safe change window · Rollback plan
Step-by-Step Instructions Step 1: Confirm Why Nameservers Need to Change Only change nameservers when there is a clear reason. · DNS migration · Hosting connection · CDN setup · Old registrar DNS replacement Step 2: Record Current Nameservers Save all old nameserver values and provider notes. · This is your rollback reference Step 3: Back Up Full DNS Zone Copy all website, email, SSL, app, verification, and DNSSEC records. · Do not rely on memory Step 4: Recreate Records at New Provider Add required records before changing nameservers at registrar. · Copy long TXT records exactly · Copy MX priorities Step 5: Check Website Records Confirm root, www, subdomains, CDN, redirects, and app records. · Test root and www separately Step 6: Check Email Records Recreate MX, SPF, DKIM, DMARC, autodiscover, and verification records. · Email records are often missed Step 7: Review DNSSEC If DS records exist, confirm the new DNS provider supports DNSSEC and keys match. · Old DS records can break resolution Step 8: Choose a Safe Window Avoid peak business, launch, or holiday periods. · Have technical staff available Step 9: Update Nameservers at Registrar Enter new hostnames exactly and save. · A typo can break DNS Step 10: Monitor Propagation and Test Check website, email, SSL, CDN, subdomains, and DNSSEC validation. · Avoid repeated changes during propagation
Troubleshooting Website Does Not Load Possible reasons: · Missing A/CNAME · Wrong nameserver · Incomplete zone · DNSSEC issue What to do: · Compare with backup · Fix records · Check domain status Email Stopped Working Possible reasons: · MX missing · Priority wrong · SPF/DKIM/DMARC missing What to do: · Restore email records · Test sending and receiving New Nameservers Rejected Possible reasons: · Typo · Nameserver does not exist · Glue missing · TLD restriction What to do: · Check spelling · Add glue for private nameservers · Contact registrar
Common Mistakes Mistake 1: Changing nameservers before copying DNS Review this item before making changes or opening a support ticket. Mistake 2: Copying website records but forgetting email Review this item before making changes or opening a support ticket. Mistake 3: Forgetting SPF/DKIM/DMARC Review this item before making changes or opening a support ticket. Mistake 4: Ignoring DNSSEC Review this item before making changes or opening a support ticket. Mistake 5: Typing nameservers incorrectly Review this item before making changes or opening a support ticket. Mistake 6: Changing during peak hours Review this item before making changes or opening a support ticket. Mistake 7: Repeated edits during propagation Review this item before making changes or opening a support ticket. Mistake 8: Deleting unknown TXT records Review this item before making changes or opening a support ticket. Mistake 9: Not testing subdomains Review this item before making changes or opening a support ticket. Mistake 10: Not keeping backup Review this item before making changes or opening a support ticket.
FAQ 1. What are nameservers? They tell the Internet where DNS records are managed. 2. Will changing nameservers make my site go down? It can if records are missing at the new DNS provider. 3. Will email be affected? Yes if MX or authentication records are missing. 4. Should I change nameservers before transfer? Only if needed, such as replacing old registrar DNS. 5. How long does propagation take? It varies based on cache, TTL, registry updates, and network behavior. 6. Can I change nameservers with DNSSEC enabled? Yes, but DS and DNSKEY must be handled carefully. 7. What if nameservers are rejected? Check spelling, existence, glue, and TLD requirements. 8. Do I need to lower TTL? It can help planned migrations if done in advance.