Guide

DNS migration checklist

Copy the zone, compare it at the new nameservers, lower TTLs and sort out DNSSEC before you change the nameservers at the registrar.

Updated

Moving a domain to a new DNS provider is one of those jobs that goes perfectly or breaks your website and email for a day. The difference is almost always preparation. The switch itself is a single change at your registrar; everything that can go wrong happens because the new provider wasn't ready when that change went live.

This checklist is for moving the DNS hosting of a domain (who answers DNS questions for it), with or without moving the registration. Work through it in order. Most of it happens before the switch, while the old provider still answers every question.

Before you start

You need three things:

  • Access to the registrar, where the domain is registered. That is where the nameservers are set. It may be the same company as your current DNS provider or a different one.
  • Access to the current DNS provider, to export or read the zone.
  • An account at the new DNS provider, with the domain added but not yet live.

Pick a quiet time for the switch, and avoid the days just before a launch, a campaign or the domain's expiry date. Check the expiry date with a WHOIS lookup: some registrars block nameserver changes on a domain that is about to expire or was just transferred.

Step 1: get a full copy of the zone

Every record has to exist at the new provider before the switch. The safest source is an export from the current provider: most offer a zone file download (often called "export" or "BIND format"). If yours doesn't, copy the records by hand from its control panel.

Don't rely on a lookup tool to find all records for you. DNS has no question that returns a whole zone, so a tool can only ask about the names it knows. Records on unusual names (a _acme-challenge, a verification record for a SaaS tool, an old subdomain someone still uses) only show up in the provider's own list.

Go through the export and note:

  • Apex records: A and AAAA for the website, MX for mail, TXT for SPF and site verifications, CAA.
  • Subdomains: www, mail, autodiscover, app and API hosts, anything your team uses.
  • Mail records: DKIM keys under _domainkey, the DMARC record at _dmarc, MTA-STS and TLS-RPT.
  • Service records: SRV records for chat, calendar or VoIP, and any verification TXT records.
  • Provider-specific records. Some providers offer things standard DNS doesn't have, such as a CNAME at the apex ("ALIAS", "ANAME" or "CNAME flattening"), redirects, or proxied records. These don't export as plain records. Find out what the new provider offers instead before the switch (CNAME at the apex explains why a real CNAME can't sit there).

Step 2: build the zone at the new provider

Add every record to the new provider exactly as it is today: same names, same types, same values. Many providers import a zone file directly; check the result afterwards, because imports sometimes skip records they don't understand or rewrite names.

Leave the old provider alone. It keeps answering every question until the switch, so nothing changes for your visitors while you work.

Step 3: compare old and new, record by record

Now ask both providers the same questions and compare the answers. The migration checker does this for you: give it the domain and the new nameservers, and it compares the records at the new nameservers with the ones the internet sees today, for the names that matter for most domains, the names your records point to, and any names you add. It flags missing records, different values, different TTLs and DNSSEC problems.

Fix every difference except the ones you mean to make. Pay special attention to:

  • MX and the mail records. A missing MX record or DKIM key means mail stops or starts failing checks the moment the switch spreads (no MX record).
  • SPF. A typo in the TXT record can make every message fail SPF. Check it with the SPF checker against the new nameservers' answer.
  • CAA. If you have CAA records, copy them exactly, or your certificate authority may refuse to renew your certificates (no CAA record explains what they do).

Step 4: lower the TTLs a day ahead

Every DNS answer carries a TTL, the number of seconds resolvers may keep it. The nameserver delegation itself has a TTL too, set by the TLD's registry, typically one or two days, and you can't change it. What you can change are the TTLs of your own records.

At least a day before the switch, lower the TTL of the records you might need to change quickly (the website and mail records) to 300 seconds at the old provider, and use the same at the new one. Wait for the old TTL to run out before you switch. If something goes wrong after the switch, a fix then reaches everyone in minutes instead of hours.

Raise the TTLs again once the move has settled, a few days later.

Step 5: sort out DNSSEC first

DNSSEC is the step that most often turns a move into an outage. If the domain is signed, the registry holds a DS record pointing at the old provider's key. When the new provider answers with a different key (or no signatures at all), resolvers that check DNSSEC treat every answer as forged and refuse to resolve the domain.

Check the domain's status with the DNSSEC checker, then take one of two paths:

  1. The simple path: turn DNSSEC off before the move. Remove the DS record at the registrar, wait for its TTL to pass (a day or two is safe), move the domain unsigned, then sign it at the new provider and add the new DS record. You are unprotected for a few days, but nothing breaks.
  2. The careful path: a key rollover between providers. Some providers support importing each other's keys, so both keys are valid during the move. This avoids the unsigned gap but needs both providers to cooperate; follow their guides exactly.

Whichever path you take, never change the nameservers while the registry still has a DS record for a key the new provider doesn't serve. The result would be a broken chain (DNSSEC validation fails, DS record matches no key).

Step 6: switch the nameservers

At the registrar, replace the old nameservers with the new provider's. Some notes:

  • Use all the nameservers the new provider gives you, usually two to four, spread over different networks.
  • Don't mix old and new nameservers in the delegation. Resolvers would ask either at random, and any difference between the two zones would show up as an intermittent fault.
  • If the registrar is also the old DNS provider, check that "use our nameservers" is switched off, or it may keep serving its own copy.

The change reaches the TLD's servers within minutes to an hour. Resolvers keep using the old nameservers until their cached delegation expires, so for a day or two some visitors reach the old provider and some the new. That is fine as long as both give the same answers, which is what steps 2 and 3 were for.

Step 7: check the result

Within an hour of the switch, check from outside:

  1. A DNS lookup for the NS records should show the new nameservers, and the records should match what you built.
  2. The delegation at the parent should agree with the NS records in your zone. If they differ, update the NS records at the new provider (parent and child NS differ).
  3. Run the email checker to confirm mail records answer correctly, and send a test message both ways.
  4. Open the website over HTTPS from a network you don't usually use, or check it with the SSL checker.

After the move

Keep the old provider's zone untouched for at least a week. Resolvers with a long cache can still ask it, and if you need to roll back, switching the nameservers back is instant if the old zone is still there.

Then finish the job:

  • Raise the TTLs back to normal values (an hour or more for records that rarely change).
  • Turn DNSSEC back on at the new provider if you switched it off, and add the new DS record at the registrar. Check it with the DNSSEC checker once the registry publishes it.
  • Remove the zone from the old provider, and cancel the service if you no longer need it.
  • Run a full domain report to see everything in one place.

A DNS move done this way is invisible to the people using your domain. The only sign it happened is a different name in the NS records.

All guides