What is an MX record and how do I change where email is delivered?

For example, an MX record at the domain apex might point to mail.example.net with priority 10. The target is a mail-server hostname, not an email address, website URL or raw IP address. The mail service must be prepared to accept mail for your domain.

Several MX records can provide the arrangement designed by your mail provider. Mixing unrelated providers does not automatically split or back up your mailboxes; the receiving servers need a deliberate routing design.

1. Create the destination mailboxes, aliases and routing before changing MX.
2. Record the current MX and related mail-authentication records.
3. Obtain the destination provider's exact MX values, priorities and required SPF, DKIM and DMARC instructions.
4. Check which DNS provider is authoritative for the domain.
5. Arrange mailbox-data migration separately if you need to retain existing messages.

Open the domain in DNS Manager and edit its MX records. Replace only the entries the migration requires and preserve unrelated website and verification records. Use the correct owner name, often the apex, and review the result before applying.

For cPanel-hosted mail, also check the account's local or remote email-routing configuration. DNS and the server's decision about accepting local mail are separate settings.

Query the authoritative MX records, then send test messages from an unrelated external account. Test replies as well. Existing senders can continue using cached MX until its prior TTL expires, so retain the old receiving service during the planned overlap.

MX changes do not copy old messages or configure users' email applications. Complete those parts of the migration through the mail platform.

If mail is rejected, check that the destination recognises the domain and mailbox. If mail goes to the old service, compare authoritative records with cached results. If outgoing messages fail authentication, investigate SPF, DKIM and DMARC rather than changing MX without evidence.

Resolve each MX target to its public A or AAAA address and confirm that the destination mail service has the recipient mailbox. A valid-looking MX row cannot compensate for an absent target or a mail server that does not accept the domain.

• Add, edit and remove DNS records in the client area
• Point your domain to a website without disrupting business email
• Understand the DNS record types used for websites and business email
• Create and verify an email forwarder for your domain

• IETF RFC 5321: SMTP mail routing