Google Workspace MX Record Problems
MX (Mail Exchanger) records tell the internet which servers should receive email for your domain. If they are wrong, missing, or pointing at an old provider, mail addressed to your domain simply never reaches Google Workspace.
Common Causes
- Old MX records from a previous host (like a web hosting provider's default mail server) never removed.
- MX records added correctly but with the wrong priority values, causing mail to route inconsistently.
- A typo in the record value, such as an extra character or missing trailing dot depending on the DNS host's format.
- Records added at the wrong DNS zone, such as a subdomain instead of the root domain.
- Recent changes that have not finished propagating.
Safe Troubleshooting Steps
- Look up your domain's current MX records using a DNS lookup tool.
- Compare them against Google Workspace's current recommended MX configuration in your Admin console.
- Remove any MX records left over from a previous email provider.
- Double check that records were added to the correct domain zone, not a subdomain.
- Allow time for propagation before re-testing - this can take up to 48 hours.
What Our Support Can Cover
- Auditing your current MX records against Workspace requirements
- Identifying leftover records from previous providers
- Confirming records were added to the correct DNS zone
- Explaining what each record does in plain language
Frequently Asked Questions
How many MX records does Google Workspace need?
Google Workspace currently recommends a single MX record pointed at Google's mail servers. Older configurations with multiple prioritized records may still work but are no longer necessary.
Can I have MX records for more than one email provider?
Generally, mail for a domain should be handled by one provider at a time. Mixed MX records from two providers usually cause unpredictable delivery rather than redundancy.