How Can We Help?
Add an MX Record
An MX record tells sending mail systems where to deliver incoming email for a domain. Use the exact mail-server values supplied by your email provider. A server name from an older Workspace Email tutorial is not a universal setting for Microsoft 365 or another email product.
Before changing an MX record
Changing email routing can interrupt delivery. Confirm which provider should receive mail, prepare the destination mailboxes, and save a record of the current DNS configuration. Change records at the authoritative DNS host; registering a domain with one company does not necessarily mean that company currently hosts its DNS.
For a standard setup, use the MX records supplied for the chosen email service rather than mixing records from unrelated providers. More complex coexistence requires a deliberately configured routing arrangement; adding multiple MX records alone does not divide recipients between two independent providers.
Add the provider-supplied MX record
- Sign in to your Domain Control Center and select the domain. If its DNS is hosted elsewhere, use that DNS provider instead.
- Open the domain’s DNS or Manage DNS section and choose Add new record.
- Select MX and enter the name, value, priority and TTL specified for your email account.
- Review any existing MX records against the provider’s cutover instructions. Do not delete unrelated DNS records or make guesses about which mail servers to keep.
- Save the change and complete any account verification required. Allow DNS caches to update before treating inconsistent test results as a failed setup.
| Field | Meaning | What to enter |
|---|---|---|
| Name or host | The domain or subdomain receiving mail | Often @ for the root domain; use the value shown in your setup instructions |
| Value or points to | The receiving mail-server hostname | The exact hostname provided for your email product, not a web address or guessed SMTP server |
| Priority | Preference among MX records | The provider’s specified number; lower numbers have higher preference |
| TTL | How long DNS answers may be cached | The value specified or supported by your DNS provider |
Verify mail flow after saving
Test delivery from an external mailbox, then send a reply from the new business mailbox. Check the expected address and any aliases. Retain access to the previous service while you verify the transition and historical data migration. An MX change affects incoming routing; it does not copy old messages or configure every outgoing-mail authentication setting.
Why is email still arriving at the old provider?
Possible causes include cached DNS answers, editing a non-authoritative zone, a typo in the new MX value, or records that still direct mail to the old service. Check the authoritative DNS settings and the account’s setup instructions before making another change. Do not add speculative duplicate records to force delivery.
Why is the website still working at the old host?
That can be correct. Website hosting and email routing use different DNS records. A change to MX records does not require moving website files or changing the website’s A or CNAME records.
Setup references
See the provider’s MX-record instructions and editing instructions. Microsoft’s custom-domain guide explains why destination users should exist before mail routing changes.