An MX record tells sending mail servers where to deliver email for your domain; email forwarding is a rule that relays a message after a mail service receives it. They are not competing settings: an MX record can direct mail to a forwarding service, which then sends it to another address.
What’s the difference between MX records and email forwarding?
| Setting or service | What it does | Where it operates |
|---|---|---|
| MX record | Identifies the mail exchanger that should receive mail for a domain. | DNS, before a receiving mail system accepts the message. |
| Email forwarding | Relays an accepted message to another address according to a service’s rules. | The receiving mail service or server, after the message reaches it. |
When sending mail, an SMTP server looks up the recipient domain’s MX records to find a destination. If the domain has multiple mail exchangers, their preference values determine their order; lower values are preferred under RFC 5321. The MX record identifies a server, not an individual inbox or forwarding rule.
Forwarding is a separate action by the mail service that receives the message. As RFC 5321 explains, a relay server is usually the target of an MX record rather than the final delivery system. This is why a mail path can include an intermediary that relays messages onward.
Do MX records forward email?
No. An MX record does not itself forward a message. It directs the sending server to a mail exchanger. That server may then accept the message and apply forwarding rules, but those rules belong to the mail service, not to DNS.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
For example, a custom-domain address can be routed by its MX record to a forwarding provider. The provider can then relay mail for a configured address to an existing personal mailbox. Cloudflare’s setup describes this pattern: MX records route incoming mail to its service, and the account owner configures forwarding rules separately (email records; route emails).
Can I use MX records to set up email forwarding?
You can use MX records as part of a forwarding setup, but the records alone are not enough. The forwarding service must also know which recipient addresses it accepts and where to send their messages.
- Choose the mail service. Confirm that it supports the forwarding behavior you need, such as aliases, catch-all addresses, destination verification, or outbound sending.
- Configure recipient rules. Add the domain and define which addresses should forward to which destinations. Verify destination addresses if the provider requires it.
- Publish the provider’s DNS records. Add the MX records the service specifies in your domain’s authoritative DNS zone. Do not copy values from another provider; record names and values are service-specific.
- Add any requested authentication records. A provider may instruct you to publish TXT records for SPF or DKIM. Follow its current setup instructions.
- Test delivery. Send a message to each configured address and confirm it arrives at the intended destination.
Cloudflare’s current onboarding documentation says its email routing setup adds MX records for inbound routing and TXT records for SPF and DKIM. Its documentation estimates DNS changes may take up to 24 hours to propagate globally, usually 5–15 minutes for domains using Cloudflare DNS; that is a Cloudflare-specific estimate, not a universal guarantee (Cloudflare Route emails).
Does forwarding create a mailbox or catch-all address?
No. MX records do not provision mailboxes, create aliases, or enable catch-all behavior. Those recipient-level features depend on the receiving provider’s configuration. Check which addresses the service accepts and whether it supports the alias or catch-all rules you want before relying on it.
Recommended Free Tools
Do I need MX records for email forwarding?
Usually, yes: mail for a domain needs an inbound route, and a forwarding service commonly asks you to point the domain’s MX records to its mail servers. The exact records depend on the provider. If another email service’s MX records remain in place, messages may continue going there instead of reaching the forwarding service.
Some business configurations route mail through an intermediate gateway or split delivery between systems. Microsoft notes that an intermediate service can legitimately receive mail first in certain configurations. Such arrangements require planning for accepted recipients, connectors, spam filtering, and responsibility for final delivery; they are more involved than forwarding a few addresses (Microsoft mail-flow best practices).
Forwarding-only service or full mailbox hosting?
| Setup | Best suited to | What to verify |
|---|---|---|
| Forwarding-only service | Receiving messages at custom-domain addresses and relaying them to existing inboxes. | Supported aliases and catch-all rules, destination verification, and whether the service offers outbound sending. |
| Full mailbox hosting | Using domain-based inboxes with storage, mailbox management, and sending. | The provider’s current MX and SMTP instructions, plus applicable SPF, DKIM, and DMARC configuration. |
| Split or relayed mail flow | Routing mail through an intermediate gateway, filter, archive, or another mail environment before final delivery. | Recipient handling, connectors, spam filtering, and operational ownership across systems. |
Choose based on whether you need to receive only or also send; whether users need separate inboxes and storage; how aliases and catch-all addresses should work; whether filtering, archiving, or split delivery is needed; and what authentication support the provider supplies.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why are forwarded messages arriving but sending fails?
Inbound routing and outbound sending are separate. An MX record directs incoming mail; it does not configure the SMTP service that sends mail from your domain. To send from a custom domain, use an SMTP provider and configure the applicable authentication records. Microsoft distinguishes MX routing from SPF, DKIM, and DMARC, which address authentication and policy (Microsoft mail-flow best practices).
Quick Recap
Best Value
What should I check if forwarding does not work?
- No messages arrive: Check that the authoritative DNS zone contains the intended provider’s MX records and that an old email-routing service is not still receiving mail.
- Only some addresses work: Check accepted recipients, aliases, catch-all policy, and forwarding rules in the mail service. MX routing does not create those rules.
- Receiving works, but sending or authentication fails: Check the SMTP provider and the domain’s SPF, DKIM, and DMARC setup; MX records do not control outbound sending.
- Changes have not taken effect: Use the DNS values and timing guidance supplied by your provider. Propagation estimates vary; Cloudflare’s published estimate applies to its service and DNS context.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
