01 / Understand the situation
What may be getting in the way
MX records direct incoming mail. SPF, DKIM and DMARC support sending authentication. None should be guessed from the website host's name. Copying an old DNS zone blindly can also reintroduce obsolete services.
02 / Start here
Concrete first steps
- Identify the email provider and preserve current DNS records. Obtain a bounce message or relevant header through a safe channel, not a public form.
- Compare MX and authentication records with the provider's official requirements and the pre-move backup. Check nameserver changes and mailbox renewal status.
- Restore necessary records, then test inbound and outbound mail with an independent address. Leave working website records intact unless a separate problem is confirmed.
03 / The work
How Blaze can help
Blaze can audit the cutover and DNS dependencies, coordinate correct records and verify mail flow. A mailbox migration, if needed, is scoped separately for aliases, folders, calendars and devices. Do not paste passwords into email or expose private mailbox contents to investigate DNS.
See website, search and workflow services, or tell us what is happening so we can scope the right work before quoting.
04 / Check the result
What to verify before calling it done
Changes may not reach every resolver simultaneously. Verification includes authoritative records, external send and receive tests and the aliases or form notifications your business relies on.
Questions you may still have
Before you decide
Must email move to the new website host?
No. Website and email can use different providers. DNS should point each service to its correct destination.
Can you recover messages sent during the outage?
It depends on provider behavior. Some sending servers retry; others may have returned a bounce. Recovery cannot be promised without evidence.
Should I replace my SPF record?
Only after accounting for every legitimate sender. Multiple conflicting records or an incomplete replacement can make delivery worse.