No MX Records Found: Why Your Domain Can't Receive Email

What MX Records Do

MX (Mail Exchanger) records are DNS records that tell other mail servers where to deliver email for your domain. When someone sends an email to user@yourdomain.com, the sending server queries DNS for your domain's MX records. The response contains one or more hostnames (with priority values) that identify the mail servers responsible for accepting email on your behalf.

Without MX records, there is no authoritative answer to "where should I deliver email for this domain?" The sending server has no destination, and the email bounces.

The fix: publish MX records pointing to your email provider's mail servers. Every email provider documents the exact records you need.

Why Missing MX Records Is Critical

When a domain has no MX records, sending mail servers return a permanent failure — typically a bounce with an error like:

550 5.1.2 Bad destination mailbox address

or:

550 Host not found

This is not a temporary issue. Every email sent to any address at your domain bounces immediately. The sender receives a non-delivery report (NDR), and no retry is attempted because the failure is permanent. Unlike spam filtering or greylisting, there is no grace period — the email never reaches any server under your control.

This affects automated systems too. Password reset emails, account verification messages, invoices, and transactional email sent to addresses at your domain fail silently from the recipient's perspective, since the bounce goes back to the sender. See the Email Bounce Codes guide for a full breakdown of SMTP error categories.

The A Record Fallback

RFC 5321 (the SMTP specification) defines a fallback: if no MX records exist, the sending server may attempt delivery to the IP address in the domain's A record. In theory, a domain with an A record but no MX records can still receive email if a mail server listens on port 25 at that IP.

In practice, do not rely on this fallback:

• Many modern mail servers and spam filters treat domains without MX records as suspicious and reject or deprioritize the connection
• The A record fallback assumes a mail server runs on the same IP as your web server, which is rarely the case with modern hosting
• Some sending servers skip the fallback entirely, especially under load or when applying strict delivery policies
• It provides no way to set priorities or specify backup servers

If your domain currently receives email via the A record fallback, publish proper MX records immediately. The fallback exists as a legacy compatibility mechanism, not as a recommended configuration.

Common Causes of Missing MX Records

New Domain Without Email Configured

The most common scenario. You registered a domain and set up a website, but never configured email hosting. Domain registrars do not create MX records by default — you need to add them after setting up email service with a provider.

DNS Migration That Dropped Records

When migrating DNS from one provider to another (e.g., moving from your registrar's nameservers to Cloudflare), MX records are sometimes left behind. If you export your zone file and the export is incomplete, or if you manually recreate records in the new provider and forget the MX entries, email stops working.

Domain Registrar Changes

Transferring a domain to a new registrar can reset DNS if the new registrar's default nameservers do not carry over your existing records. Some registrars overwrite the nameserver delegation during transfer, pointing to their own servers with an empty zone.

Accidentally Deleted Records

Someone on your team deleted the MX records while editing DNS. This happens more often than expected, especially with DNS interfaces that make it easy to select and bulk-delete records.

Expired or Suspended Domain

If your domain registration expired or was suspended, DNS resolution fails entirely — including MX lookups. The domain appears to have no MX records when the real problem is that the domain itself is not resolving.

How to Check Your MX Records

Run the mxio MX Lookup tool with your domain name. The tool queries DNS for your MX records and displays:

• All MX records with their priority values
• The hostnames each MX record points to
• Whether those hostnames resolve to valid IP addresses
• Any configuration issues or warnings

If the tool reports "No MX records found," your domain cannot receive email through normal delivery.

Use the mxio DNS Lookup tool for a broader view of all DNS records on your domain. This helps identify whether MX records are the only thing missing or if there is a larger DNS configuration problem.

How to Set Up MX Records

The exact records you need depend on your email provider. Below are the configurations for the most common providers.

Google Workspace

Google Workspace uses five MX records with staggered priorities for redundancy:

The priority value determines the order in which sending servers try each host. Lower numbers are tried first. The additional entries serve as fallbacks if the primary server is unavailable.

Microsoft 365

Microsoft 365 uses a single MX record:

Replace yourdomain-com with your actual domain, substituting dots with hyphens. Microsoft provides the exact hostname in the Microsoft 365 admin center under Settings > Domains.

Generic Mail Server

If you run your own mail server, create an MX record pointing to your server's hostname:

Ensure that mail.yourdomain.com has a valid A record pointing to your mail server's IP address. If you have a backup mail server, add a second MX record with a higher priority number (e.g., 20).

Zoho Mail

Check Zoho's documentation for regional variations (zoho.eu, zoho.in, etc.).

DNS Propagation and TTL

After adding MX records, the changes need to propagate across DNS resolvers worldwide. The time this takes depends on the TTL (Time to Live) value and caching behavior:

• New records on a fresh domain: Usually visible within 5-15 minutes
• Updated records replacing old values: Up to the old TTL value (commonly 300-3600 seconds)
• After nameserver changes: Up to 48 hours in the worst case, though typically 1-4 hours

Set your MX record TTL to a reasonable value. A TTL of 300 seconds (5 minutes) is appropriate for most configurations, allowing quick updates when needed. Avoid very low TTLs (under 60 seconds) as they increase DNS query load, and avoid very high TTLs (over 86400 seconds) as they slow down propagation when changes are needed.

Testing After Setup

After publishing your MX records and allowing time for propagation:

1. Verify MX records — Run the mxio MX Lookup tool to confirm the records are published and resolve correctly
2. Send a test email — Send an email from an external account (Gmail, Outlook.com) to an address at your domain and confirm it arrives
3. Check mail server connectivity — Verify that the mail server hostnames in your MX records resolve to reachable IP addresses on port 25
4. Review related DNS — Use the mxio DNS Lookup to check that your SPF, DKIM, and DMARC records are also configured. MX records control delivery, but authentication records control inbox placement.

If email still does not work after MX records are confirmed, the issue is with the mail server itself (not running, not accepting connections on port 25, firewall rules blocking traffic) rather than DNS.

Prevention and Ongoing Monitoring

MX records rarely change on purpose, but they disappear during DNS migrations, registrar transfers, and accidental deletions. Set up domain health monitoring to get alerted the moment your MX records are removed or modified — before email delivery breaks.

Related Issues

• Emails Going to Spam — MX records control delivery, but authentication records control inbox placement
• Email Bounce Codes — Understanding SMTP error codes when delivery fails
• Email Authentication Guide — Setting up SPF, DKIM, and DMARC after MX records are in place
• No DMARC Record Found — DMARC protects your domain from spoofing