Lorixen.
EN

Moving DNS to a New Provider Without Email or Website Downtime

Short answer: The safe way to move DNS is to make the new provider an exact copy of the old one before anything switches. Export every record a week ahead, lower TTLs at least a day or two before cutover, rebuild and compare the zone at the new host, switch off DNSSEC first if it is on, then change nameservers and leave the old zone running for several days. Email is what usually breaks, so check MX, SPF, DKIM and DMARC records twice.

Most DNS moves that go wrong fail quietly. The website loads, everyone relaxes, and two days later someone notices invoices have bounced or a supplier's emails are landing in spam. The timeline below is written for a small business moving its domain's DNS from one host to another, for example from a web host's control panel to a dedicated DNS service, or to whoever runs your new website. Cloudflare's documentation is quoted as an example because it sets out each step clearly; the sequence is the same with any provider.

Seven days before: inventory everything

Export the zone. Many hosts offer a zone file export or a BIND-format download. If yours doesn't, screenshot or copy every record into a spreadsheet: type, name, value, priority and TTL.

Find the records people forget. Automatic scans at the new provider help, but Cloudflare's own setup guide says its quick scan is not guaranteed to find every record, so treat it as a starting point. Hunt specifically for:

  • MX records for incoming mail, with their priorities.
  • TXT records: SPF (v=spf1…), DMARC (_dmarc) and verification strings from Google, Microsoft, Meta, your email marketing tool and others.
  • DKIM records, usually TXT or CNAME under a …_domainkey name. Each sending service (your mailbox provider, newsletter tool, invoicing software) may have its own.
  • CNAMEs for services: booking systems, help desks, autodiscover for Outlook, shop subdomains.
  • SRV records for phone systems or Microsoft Teams, if you use them.

Ask whoever set up each tool. A two-line email to your bookkeeper and your marketing person costs less than finding their records missing after the switch.

Check DNSSEC. Log in to your registrar and see whether DNSSEC is on and DS records are published. This decides your timing later.

Five to three days before: build the new zone

Create the zone at the new provider and add or import every record. Cloudflare, for instance, can import a BIND zone file. Then compare line by line. Its migration guidance specifically calls out MX, SRV and TXT records (especially SPF, DKIM and DMARC) and complex CNAMEs as the ones to check, plus fully qualified names with their trailing dots.

If the new provider also offers a proxy or CDN, keep it off for now. Cloudflare's guidance suggests starting with all records as "DNS only" so DNS problems and proxy problems can't be confused, then turning on the proxy for web records afterwards.

Test before you switch

You can query the new provider's nameservers directly before they are live. On a Mac or Linux machine, dig MX yourdomain.co.uk @new-nameserver returns what the new zone will answer. Compare that output with the same query against your current nameservers. Matching answers for every record name in your list is the real "ready" signal.

Two days before: lower the TTLs

TTL (time to live) tells resolvers how long they may cache an answer. If your MX record has a 24-hour TTL, some mail servers will keep using the old answer for up to a day after any change.

Cloudflare's preparation guide advises lowering TTLs on critical records at least 24 to 48 hours before the migration window, ideally longer to match your longest current TTL, and gives 300 seconds (five minutes) as a common short value. Lower them at the old provider, because that is what resolvers are caching today.

One limit to know: the nameserver delegation itself is cached according to settings at the domain's registry, which you don't control. Lower TTLs make record changes take effect faster, but the nameserver switch can still take a while to reach everyone. That is why both zones must give identical answers during the overlap.

If DNSSEC is on

Changing nameservers while DNSSEC is active can make a domain unreachable, according to Cloudflare's setup guide. The usual approach is to remove the DS record at the registrar first, then wait. Cloudflare's migration guidance says to wait at least the full DS record TTL at the parent zone, preferably up to one and a half times that, and notes the typical DS TTL is about 24 hours. Build this wait into your plan; it is often why a "Friday afternoon" switch turns into Monday. Some providers support moving with DNSSEC kept active through a multi-signer process, but that is more involved and worth a specialist.

Day 0: change the nameservers

  1. At your registrar, replace the old nameservers with the new provider's, copied exactly. A typo means nothing resolves.
  2. Leave the old DNS host's zone untouched and paid for. Resolvers that still have the old delegation cached will keep asking it.
  3. Note the time. Cloudflare says to allow up to 24 hours for the registrar update; its zone shows "Active" when the change is detected.

Do this early on a weekday, when you can watch email and the site for a few hours.

The first 48 hours: verify

  • Check delegation with dig NS yourdomain.co.uk @1.1.1.1 and @8.8.8.8, or an online propagation checker (results are often cached and can lag).
  • Send test emails in both directions from an outside address, such as a personal webmail account, and check the received headers for SPF, DKIM and DMARC passes.
  • Click through every subdomain on your list: shop, booking, client portal.
  • Re-run any domain verifications in tools like Google Search Console or your email platform if they complain.
  • Watch for bounce reports and DMARC reports if you receive them.

Day 7 onwards: tidy up

Once a week has passed with no problems, raise TTLs back to normal values on the new provider (an hour or more for stable records), re-enable DNSSEC at the new provider if you turned it off, and only then close the old DNS hosting. Keep your exported zone file somewhere safe; it is your record of what "normal" looked like.

FAQ

Will my website go offline when I change nameservers?

Not if both providers return the same answers during the overlap. Visitors reach whichever provider their resolver asks, and both point to the same server.

How long does a nameserver change take?

Often a few hours, but allow up to a day or two. Registry caching and your registrar's processing time are outside your control.

Do I have to move my domain registration as well?

No. The registrar and the DNS host can be different companies. Moving the registration is a separate process with its own timing, and is usually best done on a different day.

What about emails sent during the switch?

If the MX records are identical at both providers, mail keeps flowing. Problems come from missing or mistyped records, which is why the comparison step matters.

We regularly handle DNS cutovers as part of website launches, so if your move involves mail and several subdomains, we can plan and check it with you through our contact form.

Sources

WhatsAppLet’s talk