Changing nameservers is the one DNS edit where a small mistake can take a website and its email offline together. The good news is that it's entirely predictable. Nearly every horror story comes down to the same handful of missed steps, and a checklist avoids all of them.

Nameservers decide who answers for your domain. When you switch them, you're not editing records; you're moving the whole phone book to a new publisher. Everything must already be in place at the new one before anybody is sent there.

Step 1: Make a full inventory of your records

Before touching anything, write down every record in the current zone. Export it if your provider allows, or copy it by hand. Don't rely on a lookup tool alone: dig ANY is unreliable now because most servers return only a fraction of what exists, and it won't reveal DKIM selectors or other names you can't guess.

The ones people forget are almost always the quiet ones:

  • MX records and the email-related TXT records (SPF, DKIM selectors, DMARC).
  • Domain verification TXT records for Google, Microsoft and other services.
  • Subdomains used for staging, mail, a help desk or an old app.
  • SRV and CAA records.
  • Any records that only exist because someone added them years ago.

Step 2: Recreate the zone at the new provider

Add the new provider's zone and enter every record exactly as before. Many providers can import a zone file or pull records automatically, which is worth using, though you should always review the result by eye. Watch for differences in how the two systems treat the bare domain: a CNAME-style "alias" at the apex may be called something else.

Step 3: Test the new servers before switching

This is the step that separates a smooth move from a bad Monday. Your new provider will give you two or more nameserver names. Query them directly, bypassing the rest of the internet:

dig example.com A @ns1.newprovider.com
dig example.com MX @ns1.newprovider.com
dig example.com TXT @ns1.newprovider.com

Compare each answer with what the old servers return. Every record should match. It costs ten minutes and catches almost every error.

Step 4: Lower your TTLs

Drop the TTL on your important records to 300 seconds, at least one full old TTL before the switch. Do this on the old provider, since that's where the answers are coming from. It makes any later fix take minutes instead of hours. Our explanation of how TTL works covers the arithmetic.

Step 5: Deal with DNSSEC

If the domain is signed, this step is not optional. Remove the DS record at your registrar and wait for its TTL to expire, which is often a day. Otherwise the registry keeps advertising the old key, and validating resolvers reject answers from your new provider. After the move, turn signing on at the new provider and add its fresh DS record. The details are in our DNSSEC guide.

Step 6: Change the nameservers at the registrar

Replace the old nameservers with the new provider's, in the registrar's control panel. Use every nameserver the new provider lists, not just the first. If your nameservers are on your own domain (vanity nameservers such as ns1.example.com), you'll also need glue records, which means the registrar must hold their IP addresses.

Step 7: Keep the old zone alive

This is the most commonly skipped step. Delegations are cached for a long time: the .com registry publishes NS records with a TTL of 172800 seconds, which is 48 hours. For up to two days, a share of visitors will still be sent to your old nameservers. If those are shut down, those visitors get errors. If they're still serving correct data, nobody notices anything.

So leave the old zone up and identical for at least 48 to 72 hours. Don't cancel the old plan on the same day you make the switch, even if the new service looks perfect.

Step 8: Watch it spread

Use the NS record type in our DNS propagation checker to see which locations already show the new nameservers, and re-run A, MX and TXT checks for the important names. Our guide to DNS propagation time explains why locations update at different speeds. Check that mail still flows by sending a test message to and from the domain.

Step 9: Tidy up

  1. Raise TTLs back to normal once everything is stable.
  2. Compare registry and provider NS lists to be sure they agree.
  3. Re-enable DNSSEC if you disabled it.
  4. Only now cancel or empty the old zone.
  5. Keep a copy of the new zone somewhere outside the provider.

Questions people always ask

Will my email stop? Not if the MX and TXT records were copied correctly and the old zone stays up during the overlap. Should I do it at midnight? It doesn't help much, since delegation caching is measured in days, but a quiet hour makes any mistake cheaper. Can I move only some records? Not through nameservers; the whole zone moves. If you only need to point one name elsewhere, edit that record instead, as described in our guide to DNS record types.

A quick way to spot a bad delegation

If something feels off after the switch, ask the registry what it believes, then ask the nameservers it lists:

dig NS example.com +short
dig +nssearch example.com

The second command contacts every listed nameserver and shows its SOA serial. If the serial numbers differ between providers, or one server doesn't answer, you've found the problem. It's also worth checking your registration with the WHOIS tool, which shows the nameservers the registry currently lists. And for the bigger picture of what can break and why, see the role of DNS in website downtime.