Nameserver changes without breaking email (sanity checklist)
Short answer: Before you change nameservers or DNS hosts, snapshot every record you rely on—especially MX, SPF, DKIM, and DMARC—so email keeps flowing while the website moves.
NZ SMEs often lose a day of inbound mail because MX pointed at the old host panel and nobody exported TXT records.
Pre-flight copy
- Export zone files or screenshot all records from the current DNS UI.
- List dependencies: website, root domain email, subdomains for apps, verification tokens for Google/Microsoft.
- Lower TTLs a day or two ahead if you can—speeds rollback.
Cutover sequence
Recreate identical records at the new DNS provider first, verify with dig/nslookup against the new nameservers, then switch registrar NS delegation. Keep old DNS read-only until propagation settles.
After the change
Send test mail to and from external addresses; check webmail and device sync. Monitor bounce messages for 48 hours.
Frequently asked questions
Can we change only the website A record?
Often yes if DNS stays with the same provider—nameserver moves are the high-risk “everything at once” event.
Who should do this?
Someone who understands both domain registrar and email host—misclicks here are expensive; escalate to your IT partner if unsure.