How to Change Nameservers Without Breaking Your Website or Email Print

  • nameserver change, dns provider change, nameserver propagation, move dns without downtime, mx records lost
  • 0

A nameserver change moves everything

Nameservers are the servers that answer DNS queries for your domain. When you change them, every record moves: website, email, verification TXT records, and anything else in the zone.

If the new DNS provider does not already contain those records, the website or email will break even though the domain is still registered and paid.

This guide is for a planned move. If the site is already down, see "Domain Not Working? How to Diagnose DNS and Propagation" first.

Step 1: Inventory every record

Before touching the nameservers, export or photograph the current zone. At minimum, capture:

Record What it usually controls If lost
A / AAAA Website and hostnames Site unreachable
CNAME Aliases such as www or mail Specific hostnames fail
MX Incoming email Mail stops arriving
TXT SPF, DKIM, DMARC, domain verification Mail marked spam; services lose verification
CAA Which CAs may issue certificates Certificate issuance fails
SRV / others Voice, chat, or service discovery Specific services fail
DNSSEC / DS Signature chain at the registrar Domain can become unresolvable

Also note the TTL on each record. You will need it for Step 2.

Step 2: Lower the TTL before the move

TTL is how long resolvers cache a record. Lowering it a day before the change means the old answer expires sooner, so the new one takes effect faster.

  • Set the TTL to a low value such as 300 seconds on the records you will change.
  • Wait at least the old TTL before making the change.
  • Raise the TTL back after the new setup is stable.

Do not lower the TTL and change nameservers in the same minute. The old cached answers are still valid until their original TTL expires.

Step 3: Recreate the records at the new provider

Create the zone at the new DNS provider before changing the nameservers. For SysopHost cPanel hosting, the domain's zone is created when the domain is added to the account.

  • Recreate A and AAAA records with the same values.
  • Recreate MX records with the same priorities.
  • Recreate every TXT record, including SPF, DKIM, DMARC, and verification strings. Copy them exactly; a missing quote or space breaks them.
  • Recreate CAA records if the domain uses them.
  • If DNSSEC is active, plan the DS change separately. Do not enable DNSSEC at the new provider until the DS record matches.

For mail records, see SPF, DKIM and DMARC Setup for Google Workspace.

Step 4: Change the nameservers

  1. Log in to the registrar.
  2. Replace the current nameservers with the new ones.
  3. Save and confirm any email verification the registrar requires.
  4. Record the time of the change so you can compare it with DNS answers later.

Do not delete the old DNS zone immediately. Keep it as a rollback copy until the new setup is verified.

Step 5: Verify before you relax

dig +short NS example.com
dig +short A example.com
dig +short MX example.com
dig +short TXT example.com

Check the site over HTTPS and send a test email in both directions. If mail fails, compare the MX and TXT answers with the inventory from Step 1.

Test from more than one network if possible. A mobile connection is a quick way to avoid a local resolver cache.

Step 6: Roll back if needed

If the site or email breaks and you cannot fix it quickly, restore the previous nameservers at the registrar. The old zone still exists, so service should return after caches expire.

Rollback is faster than debugging a broken mail record under pressure. Keep the old provider active until the new one has been stable for several days.

Common mistakes

Mistake Result
Changing nameservers before creating the new zone Site and email disappear
Forgetting TXT records Mail fails authentication; verification breaks
Forgetting MX records Incoming mail stops
Leaving an old DS record Domain becomes unresolvable
Only one nameserver entered Delegation may be rejected or fragile
Deleting the old zone immediately No rollback path

Related articles

  • How to Point Your Domain to SysopHost Hosting
  • Domain Not Working? How to Diagnose DNS and Propagation
  • DNS Record Types Explained: A, AAAA, CNAME, MX, TXT, and CAA
  • DNSSEC Explained: Setup, DS Records, and Transfer Pitfalls
  • SPF, DKIM and DMARC Setup for Google Workspace

If email stops after a nameserver change, contact SysopHost support with the domain, the old and new nameservers, and the MX/TXT records you expected. Do not delete the old zone until the issue is resolved.


Was this answer helpful?

« Back