Emails Missing After DNS Change — what to check first (MX, SPF, DKIM, routing) before you lose mail
Steve H.
Reviewed for technical accuracy
Specialities: email delivery after DNS changes, MX record validation and mail routing checks, SPF/DKIM/DMARC sanity review, Microsoft 365 & Google Workspace DNS setup.
After a DNS change, missing email is usually MX routing or propagation — check which DNS is active, MX targets, and sender bounces before changing anything else
Technician
We’ll do this safely: no “wipe settings,” no random record deletions, and no repeated changes that make propagation harder to track.
First, tell me three things:
1) What email service is hosting your mail now (Microsoft 365, Google Workspace/Gmail, cPanel, Zoho, Exchange, other)?
2) Are you missing incoming mail, outgoing mail, or both?
3) What exactly changed — nameservers moved (to Cloudflare/GoDaddy/etc.), or only DNS records like MX/SPF/DKIM?
Technician
Two quick, low-risk questions (no changes yet):
1) When someone emails you, do they get a bounce/NDR (like “550,” “5.1.1,” “mailbox unavailable”), or do they get no error?
2) Where do you normally read mail — a webmail portal, Outlook, Apple Mail, Thunderbird, or a phone app?
Technician
Trust moment: I don’t want you to start “fixing” by deleting records, because that can send mail to the wrong place for longer. We’ll confirm what the internet currently thinks your MX is.
Please check one thing and tell me what you see (read-only):
• In Cloudflare DNS, do you see any MX records for your domain? If yes, what are the targets/hostnames and priorities?
Technician
MX controls where incoming mail is delivered. If MX points to an old host (or is missing/typo), mail goes to the wrong place or can be dropped.
SPF/DKIM/DMARC mostly affect whether messages are accepted as “legitimate,” but they usually cause bounces (not silent disappearance) unless mail is being delivered elsewhere.
A few targeted questions (in a different order to narrow the cause):
1) Who is your mailbox provider now — Microsoft 365, Google Workspace, or something else?
2) Did you change nameservers at the registrar (domain company), or only inside DNS records?
3) Did this start immediately after the change, or hours later?
Technician
Two safe checks that don’t change anything:
1) Confirm delegation: in your registrar, make sure the domain is truly using Cloudflare’s nameservers (no “pending” or old ones still listed).
2) Confirm the active MX on the public internet: use a DNS lookup tool to see what MX is returning right now (not just what Cloudflare shows). This tells us if propagation/delegation is the issue or the record itself.
Technician
If MX still points to the old destination, then yes — some senders may have delivered mail there. Other senders may have queued mail for a while and will retry automatically once MX becomes correct. Recovery depends on what the old mail host did (some accept and store; some reject).
Trust moment: I don’t want you to start changing multiple records at once (MX, SPF, DKIM, DMARC) because then you can’t tell what helped or harmed. We’ll isolate the problem first.
When you do the public MX lookup, also note the TTL and whether multiple MX entries show up. Mixed results can happen during propagation.
Technician
Here’s a safe way to narrow that down without “fixing” blindly:
• Ask one sender to forward you the full bounce message if they receive one (even a delayed bounce). That text is gold for diagnosis.
• Send a test email from a completely different provider (for example, Gmail to your domain). If one provider fails but another works, it can hint at reputation or DMARC alignment issues.
• Check whether missing messages are in Junk/Spam or quarantined (Microsoft 365 can quarantine). This is still “safe checking,” not changing records.
Technician
Safe order (lowest risk first):
1) Confirm the domain is using the intended nameservers at the registrar (delegation is correct).
2) Confirm what the public internet sees for MX (not just Cloudflare’s dashboard).
3) Check whether mail is landing somewhere else (old host, quarantine, spam).
Trust moment: don’t uninstall Outlook or remove accounts yet. Since webmail is also quiet, this isn’t a simple Outlook sync issue.
Technician
What matters most is doing one controlled change and then verifying the public result — not making five changes and hoping. DNS propagation varies because different systems cache for different lengths (TTL), so results can look inconsistent for a while.
If you share the symptom pattern (wrong MX publicly vs correct in Cloudflare, or mixed MX results), you’ll know whether this is a propagation/delegation issue or a record issue.
Technician
If you do just two checks and write down the results, you’ll be in a strong position:
• Public MX result (what it points to) and whether it matches Microsoft 365’s expected MX for your domain.
• Whether senders get a bounce or no bounce, plus any quarantine/spam findings.
If anything feels unclear, stop before making more changes. The safest troubleshooting is slow and controlled — especially with DNS.
Quick answer: the accepted fix
Accepted first step for emails missing after a DNS change:
• Verify the domain’s active nameservers at your registrar (make sure the DNS move is actually complete).
• Check the public MX record (what the internet sees) and confirm it matches your mail provider (Microsoft 365 / Google Workspace / etc.).
• Avoid changing multiple records at once — isolate MX first, then review SPF/DKIM/DMARC only if you see bounces or spam/quarantine symptoms.
• Collect evidence: sender bounce text (if any), timestamps, and whether mail is landing in spam/quarantine or an old mailbox.
Common reasons emails go missing after a DNS change
Most cases come down to mail routing. If the MX record points to an old host, a typo, or a placeholder, new inbound mail can be delivered somewhere else or delayed while senders retry. Another frequent cause is DNS propagation or mismatched nameserver delegation, where some senders see the new DNS and others still see the old one. Less commonly, SPF/DKIM/DMARC misalignment causes bounces, quarantine, or spam placement.
Safe checks before you edit DNS records again
Start with read-only checks: confirm nameservers at the registrar, then confirm the public MX result and TTL. Next, determine if the problem is incoming only (MX/routing) or also outgoing (SPF/sending service). If webmail and phone are both missing the same new messages, it’s not an Outlook/IMAP sync issue. Keep changes controlled: one adjustment at a time, then verify the public result.
Safety note: avoid “quick fixes” that erase evidence
DNS mail issues are solved faster when you keep clear notes.
Be careful with advice like “delete everything and re-add records.” If you remove records while mail is misrouted, you can make results harder to interpret. Instead, document what changed, capture public MX results, and save any bounce messages. If you’re using Microsoft 365 or Google Workspace, compare your records to the provider’s published DNS requirements before making edits.
Disclaimer: This information is AI-generated and intended for general guidance only. Steps vary by provider and domain registrar. For exact instructions for your setup, consult a verified expert or the manufacturer’s support site.
Getting Started Is Easy
Low-risk diagnosis
Identify whether the verification loop is driven by risk signals, cookie/session persistence, or blocked security resources.
Reduce security friction
Learn why repeated attempts can trigger cooldowns and how to test safely without escalating lockouts.
Escalation-ready notes
Collect the exact prompts, timestamps, and environment differences so official support can triage faster.
FAQ
Why did missing emails start suddenly right after a DNS change?
DNS changes often affect where inbound mail is delivered, especially the MX record. If delegation or propagation is still settling, different senders may reach different DNS answers. That can route mail to an old server or delay delivery while senders retry. Start by confirming the active nameservers and the public MX result.
Could this happen after an update or moving to Cloudflare/another DNS provider?
Yes. When you move nameservers, you must copy all required mail records correctly, not just the website records. Missing or incorrect MX is the most common cause of “no new mail.” Updates to security policies (SPF/DKIM/DMARC) can also change acceptance behavior. Verify MX first, then review SPF/DKIM/DMARC if you see bounces or quarantine.
Is this a hardware problem, or is it settings/DNS?
Almost always it’s settings and DNS routing, not hardware. If webmail and your phone both don’t show the same new messages, it’s not an Outlook sync issue. Inbound mail depends on MX records and provider routing. Check public MX and whether mail is landing in spam/quarantine before changing your devices.
Can this be fixed without a paid service or “support plan”?
Often, yes. Many cases are resolved by confirming nameservers and correcting MX to match your mail provider’s published values. The safe approach is one change at a time with public verification, plus saving any bounce text. If the situation involves an old mail host holding messages, you may need access to that old system. Documenting evidence makes any escalation faster.
Sources
- Microsoft Learn — Create DNS records at any DNS hosting provider (Microsoft 365)
- Google Workspace Admin Help — Set up MX records for Google Workspace
- Cloudflare Support — Manage DNS records
- Server Fault — Email not received after DNS/MX change (real-world troubleshooting patterns)
Filed under: Account Access Help
Related articles
- Emails Missing After Domain Change — what to check first (DNS, MX, routing) without breaking mail flow
- Emails Missing After Email Migration — Fix Outlook Sync, Online Archive & Cached Mode Issues Safely
- Emails Missing After MX Record Update — what to check first (without breaking mail flow)
- My emails are missing, but there’s no error — where did they go?
- Emails missing only from certain senders — where did they go?
- Emails Missing From Our Work Domain — what to check first (without breaking mail)
- Emails Missing from Shared Inbox? How to Restore Access Fast
- Emails Missing From Microsoft 365 — not in Inbox, Search, or folders (what to check first)
