How to move DNS without breaking email
- A day or two before: lower the TTL on the records you'll change (the A record for the website, and MX if email is moving) to 300 seconds, so the switch takes effect quickly and can be rolled back quickly.
- Read and export: run the domain through this checker, download the zone file and import it at the new DNS provider. Cloudflare, Route 53 and most others accept a BIND zone file. Compare their import against this list.
- Check the new provider has everything before you touch the name servers: MX, SPF, every DKIM key, DMARC, Microsoft 365's autodiscover and SRV records, and the verification TXT records.
- Switch the name servers at the registrar. Most changes are visible within an hour, but allow up to 48 hours.
- Compare: run the domain through this checker again. Anything marked missing needs adding at the new provider. Then send a test email to and from the domain.
The records that usually go missing
DKIM keys. Each email service (Google Workspace, Microsoft 365, Mailchimp, SendGrid, Klaviyo) has its own selector, and they sit on names you would never guess, like s1._domainkey. Lose one and that service's email starts failing DMARC.
Verification TXT records. Google, Microsoft, Meta, Apple and dozens of SaaS tools prove domain ownership with a TXT record. Remove one and nothing breaks today, but the next time the service re-checks, the domain becomes unverified.
Microsoft 365 extras. Autodiscover, the SRV records for Teams and the enterprise enrolment CNAMEs are easy to miss and annoying to track down later.
Subdomains. The shop on shop., the help centre on help., a tracking domain on links.. They're often set up by someone else and nobody remembers them until they stop working.
Questions agencies ask
You can't list a zone from outside (DNS doesn't allow it, for good reasons), so the next best thing is asking for every name that's likely to exist. This checker asks for the apex records, around 80 common subdomains, the DKIM selectors used by the main email services, DMARC, MTA-STS and the SRV records Microsoft 365 needs. If the current provider offers a zone export, use both.
Only if the email records don't make it across. Email is controlled by the MX, SPF, DKIM and DMARC records, not by who hosts the website. Copy those exactly to the new provider before switching, and email carries on as normal.
Changes to individual records follow their TTL, often an hour. A name server change at the registrar is usually visible within a few hours, but can take up to 48 hours to reach everyone. Lower TTLs a day before the move to speed things up.
Yes. In Cloudflare go to DNS, Records, Import and Export, and upload the file. Route 53, DigitalOcean, Bunny and most registrars accept the same BIND format. The name servers and SOA are left out because the new provider sets its own.
The first time you check a domain, a snapshot of its records is saved in your browser. Check it again after the move and the tool lists anything in the snapshot that is no longer being served, and anything new. Nothing is stored on this server.
They may be old: a staging site, a tool someone tried years ago, or an email service the client stopped using. Worth asking about before you copy them, but copying them does no harm.
Moving hosts, DNS or a whole platform?
I handle the technical side of migrations for agencies: DNS and email moves, hosting changes, WordPress and WooCommerce transfers and Laravel deployments, with a plan to roll back if anything goes wrong.
- White-label, under your brand, or alongside your team
- Laravel, WordPress, WooCommerce, integrations and tracking
- Inherited and half-finished sites taken over and stabilised
- UK based, straight to the developer, no account managers