Why MX records decide where your enquiries land
MX records are the delivery address for your email. They sit in your domain’s DNS and point to the servers of your email provider. If they are missing, email to your business bounces. If they point to an old provider, email quietly lands in a mailbox you no longer use.
MX records for common email providers
| Provider | Priority | Mail server |
|---|---|---|
| Google Workspace (current setup) | 1 | smtp.google.com |
| Google Workspace (older setup, still valid) | 1, 5, 5, 10, 10 | aspmx.l.google.com, alt1/alt2.aspmx.l.google.com, alt3/alt4.aspmx.l.google.com |
| Microsoft 365 | 0 | yourbusiness-com.mail.protection.outlook.com |
| Zoho Mail | 10, 20, 50 | mx.zoho.com, mx2.zoho.com, mx3.zoho.com |
| GoDaddy email | 0, 10 | smtp.secureserver.net, mailstore1.secureserver.net |
| Rackspace Email | 10, 20 | mx1.emailsrvr.com, mx2.emailsrvr.com |
Switching email providers without losing a single email
- Set up your new mailboxes first (for Google Workspace, verify the domain and create every user).
- Copy existing email across before the switch, so people see their history on day one.
- Lower the MX records’ TTL to 5 minutes a day ahead, so the change spreads fast.
- Delete the old provider’s MX records and add the new ones in the same sitting.
- Run this lookup to confirm, then copy any email that reached the old system during the switch.
This is exactly what a Googally migration does for you, usually over a weekend with no lost email.
Common MX problems
No MX records
Email bounces. Add your provider’s records at the company that manages your DNS.
Old and new provider mixed
Some email goes to each. Delete the records that belong to the provider you left.
MX points to an IP address
MX records must point to a host name, not a number. Use the name your provider gives you.
MX points to a CNAME
The target must have its own A record. Pointing MX at a CNAME breaks delivery for some senders.