What an MX record does

When someone sends a message to an address such as hello@example.com, the sending mail server needs to find a server that accepts mail for example.com. It looks up the domain’s MX (mail exchanger) records in DNS. Those records identify hostnames to contact for incoming mail. The receiving server then handles the SMTP conversation and decides whether to accept the message.

An MX record does not create a mailbox, forward messages by itself, or guarantee delivery. The named mail host must be reachable and configured to accept mail for the domain. Mailboxes, routing rules, and spam filtering are managed by the mail service rather than by the MX record.

How to read an MX record

An MX record has a domain name, a priority number, and a destination hostname. For example, an illustrative record for example.com might point to mail1.example.com with priority 10. A second record might point to mail2.example.com with priority 20. These destinations are hostnames, not email addresses or IP addresses. Each destination needs address records so a sending server can find where to connect.

The number expresses preference: a lower number is more preferred. In this example, a sending server generally tries mail1.example.com before mail2.example.com. The particular values are not important on their own; 10 and 20 express the same order as 5 and 50. The numbers are not percentages, speeds, or measures of server capacity.

What happens when there are multiple MX records

Multiple MX records can provide an alternative destination if the preferred mail host cannot be reached. A sender may try a less-preferred host after an attempt fails, or it may queue the message and retry later. The exact behavior depends on the sending system and the kind of failure it receives. A lower-priority backup is useful only if that server is ready to handle mail for the domain; merely publishing its hostname does not make it a working backup.

If two MX records have the same priority, neither has a preference over the other. Sending systems can choose between them, but equal numbers are not a precise load-balancing control. Likewise, priority does not decide which mailbox receives a message after a server accepts it. The receiving mail service makes that decision based on its own configuration.

Where MX records fit alongside other email DNS settings

MX records concern incoming delivery to a domain. They do not tell recipients whether a message sent from that domain is authorized. SPF, DKIM, and DMARC serve different roles in email authentication and policy. A domain can therefore have correct MX records while its outgoing messages still have authentication problems, or it can have outgoing mail configured without accepting incoming mail.

It also matters which domain you are checking. Mail for hello@example.com uses the MX records published for example.com, not records on the sender’s domain or on an unrelated website hostname. A website and its email can use different providers: changing a website’s address record does not necessarily change its MX records. DNS may have a default delivery behavior when no MX record exists, but relying on that behavior can make a mail setup harder to understand and maintain.

A practical checklist when mail is not arriving

First, check the MX records for the exact domain after the @ sign in the affected address. Compare their destinations and priority numbers with the settings supplied by the mail provider. Look for old records left behind after a provider change, misspelled hostnames, or a backup record that points to a server not configured for the domain. If a provider asks you to use specific MX records, avoid adding extra ones on the assumption that more records improve delivery.

Next, check that each MX destination resolves to an address and that the intended mail service is operating and accepts mail for the domain. If you recently changed DNS, cached answers may cause different senders to see different records for a while; the record’s TTL influences how long an earlier answer may be retained. Finally, inspect any delivery error returned to the sender. A DNS lookup problem, a connection failure, and a server rejecting a recipient are different issues, even though each may appear to the recipient as a missing message.

Back to category ↗