Moving your domain's DNS management to a new provider — whether for better tooling, pricing, or consolidating with your VPS host — can be done with zero downtime if planned correctly.
Why Migrate DNS Providers
- Better API access for automation
- Improved DNS query performance/global anycast network
- Consolidating domain and hosting management with one provider
- Advanced features (DNS-based load balancing, geo-routing)
Step 1 — Document Every Existing DNS Record
Before touching anything, export or manually record every record at your current provider:
dig A yourdomain.com
dig AAAA yourdomain.com
dig MX yourdomain.com
dig TXT yourdomain.com
dig CNAME www.yourdomain.com
dig NS yourdomain.comMany DNS providers also offer a zone file export option — use it if available, as a more complete and reliable record than manual documentation.
Step 2 — Lower TTL Values in Advance
At least 24–48 hours before migrating, lower the TTL on all records at your current provider to something short (e.g. 300 seconds). This ensures that once you do cut over, cached DNS resolvers worldwide refresh quickly rather than serving stale data for hours.
Step 3 — Create the New DNS Zone at the New Provider
Add every record from your documentation to the new provider — A, AAAA, CNAME, MX, TXT (including SPF/DKIM/DMARC), and any others.
Step 4 — Verify the New Zone Before Switching
Most DNS providers let you test records before they're live — verify against the new provider's nameservers directly:
dig yourdomain.com @newprovider-ns1.comStep 5 — Update Nameservers at Your Registrar
This is the actual cutover step — change the nameservers listed at your domain registrar to point to the new DNS provider's nameservers.
Step 6 — Monitor the Transition
dig NS yourdomain.comWatch until this consistently shows the new nameservers globally. Since you lowered TTL in advance, this typically completes faster than a default migration.
Step 7 — Verify Everything Works
- Website loads correctly:
dig +short yourdomain.com - Email still routes correctly:
dig MX yourdomain.com - SPF/DKIM/DMARC still pass: send a test email and check headers
Step 8 — Raise TTL Back to Normal
Once confirmed stable (allow a few days), raise TTL values back to a more standard duration (e.g. 3600–86400 seconds) at the new provider.
Step 9 — Keep the Old Provider's Records for a Grace Period
Don't delete the zone at your old DNS provider immediately — keep it intact for a week or two in case you need to quickly revert, even though the registrar now points elsewhere.
Common Errors
Email stops working after migration — an MX or SPF/DKIM/DMARC TXT record was missed during the copy; recheck against your original documentation.
Some visitors see the old site, others see the new one — expected temporarily during propagation if TTL wasn't lowered in advance; wait for full propagation.
Domain becomes completely unreachable — a critical record (usually the root A record) was missed; add it immediately at the new provider.
Best Practices
- Always lower TTL well in advance of a planned migration
- Double, then triple-check every record was copied correctly before cutover
- Migrate during a low-traffic period as an extra precaution
- Keep the old zone available as a fallback for at least a week
Related Articles
- DNS Fundamentals: A, AAAA, CNAME, MX, TXT & NS Records Explained
- How to Troubleshoot DNS Propagation Issues
- How to Configure SPF, DKIM, and DMARC (Complete Guide)
