Website or Email Stopped Working After DNS Change? What to Check

If your email stopped working after a DNS change, check the mail records separately from the website records. The two services can fail for different reasons even though they share a domain. Work out whether nameservers changed, individual records changed, or both. Keep a copy of the previous zone and note the time of each edit.

Email stopped working after a DNS change? Confirm nameservers

Find where the domain’s live DNS is hosted. Records left at a previous provider do not affect visitors after nameservers move. Compare the active zone with the old copy, including website, mail and verification records. Correct missing records at the authoritative provider before waiting for caches to update. Check that the zone belongs to the correct domain.

Check the website route

Inspect A, AAAA and CNAME answers for root and www. Confirm they reach the intended server and HTTPS has a certificate for the requested name. If the site redirects repeatedly, compare hosting, WordPress and proxy rules rather than changing unrelated DNS records. Test an internal page as well as the homepage.

Email stopped working after a DNS change: mail checks

Compare public MX records with the mail provider’s required values. Review SPF, DKIM and DMARC for outgoing mail. A successful website test does not confirm inbound mail works. Send a labelled external message and reply, then inspect any non-delivery report. Confirm that form notifications still reach the correct inbox.

Account for cached answers

If email stopped working after a DNS change, cached answers can explain inconsistent results. A resolver may use an old answer until TTL expires. Compare the authoritative answer with several public resolvers and another network where useful. If the authoritative answer remains wrong, propagation is not the explanation. Avoid repeatedly changing values while old answers are circulating.

Verify connected services

Website forms, transactional mail, analytics, payment callbacks and verification records may rely on the domain. Test paths the business uses and record results. Keep old hosting available until the new site, email and forms are confirmed on the public domain. Make changes in a controlled order and retain a rollback record.

Related: DNS and hosting support and DNS propagation explanation.

Check mail-specific proxy settings

If you use Cloudflare, its standard web proxy does not carry SMTP, IMAP or POP3 traffic. Mail hostnames need the provider-appropriate DNS configuration, not the same proxy setting as a website. Compare your records against your mail provider and the Cloudflare email troubleshooting guidance before changing them. Do not copy another business’s MX values.

Explain why email stopped working after a DNS change

If email stopped working after a DNS change, provide the affected domain, change time and exact delivery error. State whether incoming mail, outgoing mail or both fail. Include which provider should handle email and whether the website still works.

Ask the administrator to compare the old and active records before making another broad change. A nameserver move may have omitted mail records even when the website record is correct. Correct the identified difference, then repeat the external send-and-receive test. Keep the result with the change record so the next migration does not repeat the same omission.