Email stopped working after moving DNS to Cloudflare: when this repair path applies
Restore the mail provider records in Cloudflare DNS without changing the working website records. Use these steps when website resolves but mail does not, but first run the embedded diagnostic so the business-email DNS and mail authentication evidence supports this provider-specific path rather than a neighboring DNS, TLS, application or mail cause.
Find the authoritative setting before editing
Cloudflare DNS > Records for DNS changes, and SSL/TLS or Rules only when the diagnosis specifically points to those layers. For Email stopped working after moving DNS to Cloudflare, confirm the active nameservers and exact service owner before changing compare the previous and current MX records. A DNS-looking screen at cloudflare has no public effect when another provider is authoritative for the zone.
Evidence to save for Email stopped working after moving DNS to Cloudflare
Record the current public state for compare the previous and current MX records, restore MX, SPF, DKIM and DMARC, keep mail hostnames DNS-only where the provider requires it. This gives the repair a before/after comparison and prevents a cached answer or a separate working service from being confused with the configuration that produced the symptom.
- Compare the previous and current MX records — Read the public MX priorities and targets, then verify that each target itself resolves. A visible MX record is not enough if its mail hostname is broken.
- Restore MX, SPF, DKIM and DMARC — Read the public MX priorities and targets, then verify that each target itself resolves. A visible MX record is not enough if its mail hostname is broken.
- Keep mail hostnames DNS-only where the provider requires it — Verify keep mail hostnames DNS-only where the provider requires it from the public Internet and compare it with the value the responsible provider says should be live.
Repair steps in cloudflare
Restore the mail provider records in Cloudflare DNS without changing the working website records.
- 1. Compare the previous and current MX records. After this step, check the public value tied to compare the previous and current mx records before changing another unrelated setting.
- 2. Restore MX, SPF, DKIM and DMARC. After this step, check the public value tied to restore mx, spf, dkim and dmarc before changing another unrelated setting.
- 3. Keep mail hostnames DNS-only where the provider requires it. After this step, check the public value tied to keep mail hostnames dns-only where the provider requires it before changing another unrelated setting.
Why this order matters for cloudflare
The sequence begins with the provider/authority decision, then moves through compare the previous and current MX records, restore MX, SPF, DKIM and DMARC, keep mail hostnames DNS-only where the provider requires it. That keeps the change scoped to the failed business-email DNS and mail authentication path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.
Verify Email stopped working after moving DNS to Cloudflare
The public MX/authentication records should match the intended mail provider, required hostnames should resolve, and the relevant SPF/DKIM/DMARC check should no longer show the original failure. Compare the same compare the previous and current MX records and restore MX, SPF, DKIM and DMARC evidence used before the change; a repair is complete when the public result agrees, not merely when the cloudflare interface reports that a save succeeded.
If cloudflare and the public result disagree
Check whether the edited zone is authoritative, whether the exact root/www/subdomain was changed, whether a proxy state alters the visible endpoint, and whether a prior TTL can still exist in recursive caches. Do not add a second conflicting compare the previous and current MX records value to force validation.
Mistakes to avoid for this repair
Do not copy tenant-specific or region-specific values from another account, delete working email records during a website repair, change nameservers as a shortcut, or alter SSL/proxy modes without evidence from the origin. Email stopped working after moving DNS to Cloudflare should change only the settings required by this diagnosis.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.