Introduction

When email stops working after a DNS change, the website may still load normally, which makes the issue easy to miss. Mail delivery depends on more than one record. MX, SPF, DKIM, DMARC, autodiscovery, and provider-specific verification records can all matter. The safest fix is to verify the full mail configuration against the intended provider instead of restoring only one visible record.

Symptoms

  • Incoming mail stops arriving after a DNS migration or nameserver change
  • Outbound mail fails, lands in spam, or shows authentication warnings
  • One mailbox provider works while another does not
  • The website is online, but email routing changed unexpectedly
  • The issue started after moving DNS hosting, web hosting, or email providers

Common Causes

  • MX records are missing, wrong, or still point to the previous mail provider
  • SPF, DKIM, or DMARC records were lost during the DNS cutover
  • DNS propagation or delegation changes send different resolvers to different mail answers
  • Required provider-specific records for mail routing or verification were never recreated
  • TTL and cache differences make part of the internet use the old mail path longer than expected

Step-by-Step Fix

  1. Confirm whether the problem affects incoming mail, outgoing mail, or both, because those usually depend on different DNS records and systems.
  2. Compare the live MX, SPF, DKIM, and DMARC records with the exact values required by your intended mail provider.
  3. Query authoritative nameservers directly so you can see whether the active zone really contains the needed mail records after the DNS change.
  4. Check whether old and new nameserver sets are both being queried anywhere, which can create mixed mail-routing behavior during migration.
  5. Recreate any missing provider-specific records for routing, verification, or autodiscovery instead of restoring only the MX entry.
  6. Validate outbound authentication alignment so mail from the domain is still trusted after the DNS cutover.
  7. Retest with a few controlled inbound and outbound messages only after the authoritative DNS answers are correct.
  8. Monitor bounces, spam placement, and provider admin alerts while the new DNS state finishes propagating.
  9. Keep a documented mail DNS inventory so future DNS moves do not break email while the website still appears healthy.