What Is an MX Record and Why Does Email Stop Working After DNS Changes?

If a website still loads after a DNS change but email suddenly stops arriving, the first record type to investigate is usually the MX record.

That is because MX records control where inbound mail should be delivered.

The simple definition

An MX record tells the internet which mail server should receive inbound email for a domain.

Without a valid MX path, inbound mail delivery can fail even if the domain still resolves for web traffic.

That is why mail issues often appear after otherwise successful DNS changes.

Why web and email can break differently

Website traffic and email traffic do not use the same DNS path.

A site can keep working because the A, AAAA, or CNAME records for web delivery are still correct, while email breaks because:

• the MX records changed
• the MX records were removed
• the nameserver change pointed the domain at a zone missing the email records

That separation is the key operational idea.

Why MX records matter so much

If you use a managed email platform, the provider usually gives you specific MX values to publish.

Those values tell mail senders where to route messages for your domain. If they are missing or wrong, inbound delivery can fail regardless of whether your website still looks healthy.

Some providers also require accompanying TXT records for SPF or routing support, which is why mail breakage can involve more than one record type.

The most common break scenario

The classic failure looks like this:

1. a domain or nameserver migration happens
2. the main website records are recreated first
3. the MX records are missing, incomplete, or overwritten
4. inbound email stops or behaves unpredictably

This is not rare. It is one of the most common DNS migration mistakes.

What to check first when mail stops working

1. Confirm the authoritative nameservers

Before checking the MX values themselves, confirm which nameservers are authoritative right now.

If the domain is using the wrong DNS provider or a partially rebuilt zone, the MX records you expect may not be the ones the internet is actually seeing.

2. Check whether MX records exist at all

If no valid MX records are published for the domain, inbound email delivery has nowhere clear to go.

3. Compare the MX values with the email provider’s documented setup

Do not guess from memory. If the provider expects specific hostnames or priorities, the published values need to match.

4. Check for conflicting mail-routing changes

Some email-routing or forwarding products can require new MX and TXT records, and existing mail services may need to be removed or updated during the change.

That is why email migrations can break even when the DNS edit looked small.

Why nameserver changes are especially risky

When nameservers change, the internet starts trusting a different authoritative DNS source for the domain.

If the new zone does not already contain the correct MX and supporting records, mail can break immediately even though the change itself succeeded technically.

This is why What Is a Nameserver and Why It Matters? belongs next to any MX troubleshooting checklist.

How this shows up in domain lookup

In Domain Lookup, the email section is valuable because it quickly reveals whether the domain has visible MX posture at all, and whether the broader DNS footprint looks complete enough to support mail.

That is often the fastest way to decide whether the problem is mail routing, DNS authority, or a provider-side configuration mismatch.

Common misunderstandings

"If the website works, email should work too"

No.

Web delivery and email delivery rely on different DNS records.

"A nameserver migration only affects DNS management, not mail flow"

No.

A nameserver migration changes which authoritative zone the internet trusts, and that directly affects MX answers.

"If MX exists, mail must be fine"

Not necessarily.

The MX values can still be wrong, incomplete, or inconsistent with the provider’s expected setup.

FAQ

What does an MX record do?

It tells mail senders which server should receive inbound email for the domain.

Why did email stop after a DNS change?

One common reason is that the MX records or related mail DNS records were changed, removed, or left out during the migration.

Can email break while the website still works?

Yes. Website records and email records are separate, so one can be healthy while the other is broken.

Should I check nameservers before checking MX values?

Yes. If the wrong nameservers are authoritative, the MX records you expect may not be the records the internet is actually using.