How do I change DNS records without breaking my email?
Save a copy of every record before touching anything. Change only the records the job needs, and leave MX, SPF, DKIM and DMARC alone unless email itself is moving. For a nameserver switch, compare the new zone against your copy line by line. Lower the TTL at least one TTL ahead, then test website and email afterward.
What are the steps?
This page is about doing changes safely. For adding records a new service asks for, see how to add DNS records for a new email or marketing service.
- Save a copy. Note each record’s type, name, value and TTL.
- Know which records do what. A and CNAME records point your website. MX records decide where email is delivered. TXT records hold SPF, DMARC and verification codes. DKIM uses TXT or CNAME records depending on your email provider (Microsoft 365 uses two CNAMEs), so save those too. Read what DNS is.
- Lower the TTL ahead of time on the records you’ll change, at least as long before as the current TTL (a record with a two-day TTL needs two days), so the switch, and any undo, spreads faster. See why DNS changes take time.
- Make one change, check it, then move to the next.
- Test afterward. Load the site on mobile data, send mail to your business address from an outside account and reply, and submit your contact form.
- Raise the TTL back to normal once everything works.
The short version
- Export or screenshot every DNS record first. That’s your undo.
- Change only what the job needs; a website move usually means the A record and “www.”
- Treat nameserver changes as moving the whole zone, and check every record arrived.
- Make one change at a time, then test website and email.
How do I change nameservers safely?
Changing nameservers moves your entire DNS to a different provider, which starts with only the records you add. Cloudflare can scan for existing records, but its setup guide says the scan “is not guaranteed to find all existing DNS records.” DKIM keys and verification codes are easy to miss. Compare the new zone with your saved copy before you switch.
If DNSSEC is on, turn it off at the registrar before the switch; Cloudflare warns the domain can become unreachable otherwise.
Why does it matter?
Website and email records live side by side. A change meant for the website can quietly stop mail, and you may not notice until a customer asks why you never replied.
What are the common mistakes?
- Deleting “unknown” records that turn out to be DKIM keys or Microsoft verification.
- A second SPF record for a new service instead of editing the first. See what SPF, DKIM and DMARC are.
- Changing records at the wrong company, when the nameservers point somewhere else.
- Several changes at once, so nobody knows which one broke things.
What if email stopped after a change?
Compare the live records with your copy and restore the MX, SPF and DKIM entries first. Then wait for cached answers to expire. Our free email deliverability checker confirms the email records are back. If mail is bouncing, see why messages bounce.
How much does it cost, and how long does it take?
DNS changes cost nothing at most providers. A careful move adds waiting time beforehand for the old TTL to run out, as long as that TTL (often an hour to a day); each change takes minutes.
How does E-3 handle this?
On any DNS job, we save the existing records first. The saved copy of the old records means we can put them back if anything goes wrong. Planning a move? Read how to move your website to a new host.
Related questions
Common questions
- What's the most common DNS mistake?
- Switching nameservers to a new provider without copying every existing record first. The website may work, but email records get left behind and mail stops.
- How do I undo a bad DNS change?
- Put the old values back from your saved copy. Recovery is quicker if you lowered the TTL beforehand, because cached answers expire sooner.
- Should I turn off DNSSEC before changing nameservers?
- If DNSSEC is on, yes. Cloudflare warns that changing nameservers with DNSSEC active can make your domain unreachable. Turn it off at the registrar first, then back on afterward.
Rather talk it through?
Call our team, or send a note and we’ll reply within one business day. No pressure and no jargon.