Domains · Practical guide
DNS migration checklist: move nameservers without losing email
Treat DNS as a production dependency. Most migration outages come from missing records, incompatible DNSSEC settings or testing only the homepage.
First published · OlaCheap technical reference · Check current provider instructions before changing production services
Capture the current zone and identify dependencies
Export the full DNS zone if possible. Compare it with public responses for apex, www, mail, autodiscover and any application subdomains. Include SPF, DKIM, DMARC, payment, analytics and website-verification TXT records. A website can appear healthy while email authentication silently breaks.
Identify which records are managed by the hosting provider versus records that have been placed manually. Some providers create hidden or flattened records: a screenshot of a dashboard may not reproduce the actual publicly served DNS. Confirm the authoritative answers independently.
Verification checklist
- A/AAAA, CNAME, MX, TXT, CAA and SRV where used
- DKIM selectors and _dmarc TXT
- Wildcard records, verification records and DNSSEC DS records
Prepare the destination before switching
Build the target zone in the new DNS provider and compare record values and priorities. For mail, MX priority ordering matters. For web, check AAAA if IPv6 is offered; an obsolete AAAA record can send some visitors to the old server even when the A record is correct.
A lower TTL may reduce how long some caches retain old answers, but it is not a guaranteed cutover timer. Change TTL in advance and leave the old origin available during the transition. Never delete the old provider's zone immediately after updating the delegation.
Change authoritative nameservers and test from outside
Update the registry delegation to the intended nameservers. Check the current NS answer and trace it through authoritative servers, not just from a workstation cache. Run tests through more than one public resolver or network.
Inspect the site with a fresh HTTPS session; send test messages from an unrelated mail provider; check DMARC alignment and incoming spam filtering. For domain ownership flows, verify that all required TXT records remain visible. Take note of any external provider that signs DKIM or requires a custom bounce domain.
Verification checklist
- Validate both apex and www over HTTPS
- Test outside-to-inside and inside-to-outside email
- Check domain-verification tokens and DNSSEC chain of trust
Plan rollback before the change
Write down the original nameservers, keep the previous zone available and decide exactly what conditions trigger a rollback. If the destination lacks an essential record, restoring the previous NS delegation can help, but DNS caches may temporarily continue using either side.
If the old DNS provider hosts records needed by your email service, maintain that service until the new zone and account ownership are verified. Removing an old account prematurely can turn a reversible configuration mistake into a wider outage.
Next practical step
This article is an educational checklist, not a claim of live product availability or a substitute for current documentation from your provider.
Find domain and DNS management options →References and official documentation
These materials help verify procedures. Provider requirements may change, and this guide does not claim first-hand security certification or independent testing of third-party products.