Many domain owners assume that moving a website also requires moving
email. It does not. Website hosting and email hosting are separate
services connected through DNS.
Understanding that separation prevents one of the most frustrating
migration failures: a successful new website paired with missing
incoming email.
This answers questions such as ‘can I move my website without moving
email?’, ‘why does email still work after changing web hosts?’, and
‘does one company have to host both?’ DNS routes the services
independently.
The four roles behind one
domain
A single domain can involve several providers:
- The registrar manages domain registration and
renewal. - The DNS host publishes the domain’s DNS
records. - The web host stores and serves the website.
- The email host sends, receives, and stores
mailboxes.
One company may perform all four roles, but it is not required. The
domain works because DNS points each service to the appropriate
provider.
Which records control the
website?
The root domain and www hostname normally use A, AAAA,
or CNAME records to reach the web host. Changing these records can move
web traffic without altering mail delivery.
The exact structure depends on the host. Follow the values supplied
for the specific domain and account rather than copying records from an
unrelated website.
Which records control email?
MX records tell other mail systems where to deliver incoming mail.
TXT and CNAME records may authenticate outgoing mail through SPF and
DKIM, while DMARC tells receivers how to handle authentication failures
and where to send reports.
Autodiscover, webmail, and provider-verification records may also
exist. Preserving only the MX records is not always enough for a fully
functioning and properly authenticated email setup.
Why nameserver changes
create risk
Nameservers identify which DNS provider is authoritative for the
domain. Replacing them does not merely change the website destination;
it tells the internet to use an entirely different DNS zone.
If the replacement zone lacks the old email records, incoming mail
can fail. The correct preparation is to inventory the existing zone and
reproduce every required record at the new DNS host before switching
nameservers.
Alternatively, when appropriate, retain the current nameservers and
change only the website records. The right choice depends on who should
manage DNS long term.
A safe website-only
migration sequence
- Confirm the current registrar, nameservers, web host, and email
host. - Export or document the complete DNS zone.
- Identify all website records and all email-related records.
- Build and test the new website before directing public traffic to
it. - Create a current website backup.
- Change only the records required for web traffic.
- Verify the site, HTTPS,
www, and redirects. - Test incoming and outgoing email with an external account.
- Keep the old hosting environment available during the agreed
rollback window.
How to test email after
a website move
Send a message from the domain mailbox to a Gmail, Outlook, or other
external account, then reply to it. Confirm that both directions work
and that the messages are not rejected.
Check the message headers or an email-authentication testing service
to verify SPF, DKIM, and DMARC. A message arriving successfully does not
guarantee that authentication is correct.
Do not “clean up” unfamiliar
records
An unfamiliar TXT or CNAME record may support mail authentication,
account verification, a subdomain, or another active service.
Documentation comes before cleanup.
If a record appears obsolete, identify the service owner and verify
that it is no longer needed. Remove it in a separate, documented
maintenance change—not during an unrelated website migration.
The practical lesson
A domain is not a single service. Treat the website and email as
separate systems, even when one company currently hosts both. That
mental model makes provider changes safer and makes troubleshooting much
faster.
Create a service ownership
inventory
Keep a private record showing the registrar, authoritative DNS host,
website host, email provider, certificate management method, and
administrator responsible for each service. Include renewal dates and
recovery procedures, but never publish passwords, recovery codes,
private keys, or full account identifiers.
This inventory prevents the common mistake of contacting the
registrar about a mailbox problem or editing the web host’s DNS panel
when another provider is authoritative.
Frequently asked questions
Will changing
my web host change my email address?
Not if the email service and its DNS records remain intact. Test both
incoming and outgoing mail after any DNS change.
Can I cancel the old host
immediately?
Usually that is unnecessarily risky. Keep the old environment
available through a defined validation and rollback period, then cancel
only after confirming files, databases, redirects, certificates, and
email behavior.
Who controls
DNS if my registrar and host differ?
The authoritative nameservers determine where records are managed.
Look up the current delegation and confirm the active DNS provider
before editing anything.
Related guides
- DNS
Changes Without Breaking Your Website or Email - How to Verify a Domain in Google Search Console