Move a Website Without Breaking Email: The DNS Checklist
You can move a website to a new host and keep its email service where it is. The website and mailbox may use the same domain name, but they can rely on different servers and DNS records. The risk in a move is changing nameservers or replacing a DNS zone without carrying over the mail records. This checklist is for a live domain with working email that you want to preserve while changing the web host.
Know which service is moving
| Component | What it controls | Change it for a website-only move? |
|---|---|---|
| Registrar | Domain registration and access to nameserver settings | Usually no |
| Authoritative DNS | Where the domain’s DNS records are published | Only if you deliberately move DNS management |
| Website host | Site files, application and database | Yes |
| Email provider | Mailboxes and messages | No, if you want to keep the existing mail service |
A domain transfer changes which company is the registrar. A nameserver change changes which DNS service answers for the domain. Neither is inherently required just to point a website to another server. See our domain transfer versus DNS change guide for the decision tree.
Record the mail settings before touching DNS
Export or take a clear record of the current DNS zone, especially the MX records that route incoming mail, the TXT records used for SPF and domain verification, any DKIM and DMARC records, and provider-specific names such as Autodiscover. Exact records vary by email provider. Cloudflare’s DNS guide describes the common email records, while Microsoft lists its required external mail records. Copy the values from your own email admin panel rather than from a blog example.
Also identify where mailboxes are actually billed. If your email subscription was sold through the old web host, leaving its website plan may affect the mailbox account even when DNS still points correctly. Ask the old provider in writing whether the mailbox remains active on a separate plan and how to export existing messages. DNS controls delivery; it does not preserve a mailbox after its service is canceled.
Safer route: change only the website records
- Build the site at the new host and test it on a temporary address or hosts-file preview. Confirm pages, forms, checkout, images and downloads before switching visitors.
- Back up the website and database, plus a separate export of mail if its account could change. Record current DNS values and keep access to both hosts.
- In the current authoritative DNS zone, update only the website-related A, AAAA or CNAME records that the new host requires. First check whether a record you plan to change also names the mail server or is targeted by MX, SMTP, IMAP or POP settings; some setups share a hostname or IP between web and mail. Coordinate a separate DNS-only mail hostname with the email provider if needed. Keep MX, SPF, DKIM and DMARC accurate for the mail service that will remain. Cloudflare explains this shared-hostname case.
- Allow for DNS caching. Test the website and send mail in both directions from an outside account. Check more than one network if timing matters.
- Keep the old website account until the new site and email both work and you have a rollback copy. Then cancel only the service you no longer need.
This route preserves the DNS provider and avoids wholesale recreation of the zone. The exact record names depend on whether your site uses the root domain, www, a CDN or another proxy. Follow the new web host’s instructions for those website records.
If you must change nameservers
Create the entire zone at the new DNS provider before changing the registrar’s nameserver setting. Compare each mail record with the old zone, including TXT records with multiple values and any subdomains used for mail. Cloudflare’s full DNS setup guide describes reviewing imported records before delegating the domain. Do not assume an automatic scan found everything.
After the switch, check authoritative DNS and test inbound and outbound mail. A website may load correctly while MX or authentication records are missing. Cloudflare’s email troubleshooting guide distinguishes missing routing records from SPF, DKIM and DMARC issues. If messages stop arriving, compare the new zone with the original record inventory first; if messages are rejected or land in spam, inspect authentication records and the email provider’s logs.
What if you are changing email providers too?
That is a separate mailbox migration. Plan user accounts, existing message transfer, aliases, calendars and devices before changing MX. The DNS cutover changes where new mail goes, but older messages remain at the previous provider unless you migrate them; Microsoft’s domain setup documentation makes that distinction explicitly. A website migration service may not include any of this work. Read our free migration scope checklist and get the answer in writing.
Before you buy a replacement host
Ask whether the host requires a nameserver change or supports pointing only the site records, whether it will migrate mailboxes, and what email costs after any introductory period. For a business that depends on mail every day, keep the website and email decisions separate on the budget sheet. Our renewal calculator can include ongoing mailbox charges, and our full migration checklist covers the site cutover and rollback.
Sources checked September 25, 2026: Cloudflare email DNS records, DNS zone setup and email troubleshooting; Microsoft 365 external DNS records and domain setup. Use your own provider’s current record values.