Help for owners
My business email stopped working after I moved my website to a new host
Short answer
Mail is delivered to whatever your domain's MX records name. A hosting move that replaced the DNS zone often drops those records, or leaves them pointing at a server that no longer holds your mailboxes. Do not delete anything. Compare the old DNS records with the new ones and restore the missing mail ones.
Does this sound like your situation?
- People say my emails to them bounce, or theirs to me never arrive.
- My mailbox is empty since the day the site moved.
- The old host's webmail still shows mail I cannot see anywhere else.
- I can send but not receive, or the other way round.
- Mail from my domain lands in spam since the move.
Why does this happen?
The MX records were lost or point to the wrong server
Google explains that senders use MX records to find where to deliver a domain's mail, and that old or incorrect MX records can stop mail working correctly. After a nameserver change the new zone may not have them.
Confirmed by knowledge.workspace.google.com
DNS changes spread slowly
Resolvers keep a record for its TTL. Some senders still use the old value while others see the new one, which explains mail that works for some people only.
Confirmed by docs.aws.amazon.com
The mailboxes stayed on the old host
If the old hosting account provided the mailboxes and it is closed or its MX removed, mail has nowhere to go.
Authentication records were not copied
SPF, DKIM and DMARC records are separate DNS entries. If they are missing, the messages you send can be rejected or filtered as spam.
What can I do about it today?
- Do not close the old hosting accountIt may still hold mailboxes and old mail.
- Get both sets of DNS recordsAsk for the records at the old host and the current ones, so they can be compared line by line.
- Look for MX and TXT linesIf the new list has no MX lines, or fewer TXT lines than before, you have likely found the gap.
- Tell people to resendAsk key contacts to resend anything important. Some senders keep trying for a while, others give up.
- Wait for the changes to take effectAfter a fix, allow time for DNS caches. Google says up to 72 hours for new MX records to be recognised.
When should I bring someone in?
- Important customer email has gone missing.
- Mail works for some people and not others, and you cannot see why.
- Mail you send is being rejected or marked as spam.
How do I handle it?
- Compare old and new DNSEvery record from the old zone is checked against the new one, and I note which are missing.
- Restore routing firstMX records go back to the correct mail provider, so incoming mail flows again.
- Restore authenticationSPF, DKIM and DMARC are checked and rebuilt to match the provider that sends your mail.
- Recover stored mailMessages remaining on the old server are exported before that account closes.
- Test both directionsMessages are sent to and from outside providers and the headers checked.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is my old mail lost?
Usually not, if the old mailbox still exists. Mail sent during the gap may be delayed, bounced or lost depending on the sender, so ask important senders to resend.
Why does it work on my phone but not for others?
Different resolvers hold the old record for different times, so results vary until caches expire.
Could the site move itself have caused this?
The site and email are separate, but a nameserver change replaces the whole DNS zone, which is how email gets affected.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.