MX Record Conflict When Setting Up Google Workspace or Microsoft 365? Here's the Fix

You're partway through setting up Google Workspace or Microsoft 365 for your domain's email, following the setup wizard step by step, and it stops you cold: an MX record conflict, or a warning that records already exist for this domain. Mail starts bouncing, or arrives inconsistently, and the setup that was supposed to take twenty minutes is now a troubleshooting session.

Why MX Conflicts Happen

MX records tell the internet where to deliver email for your domain, and they work on a priority system — lower numbers get tried first. When you switch email providers, the old provider's MX records often stay in your DNS panel untouched, because switching email doesn't automatically remove them. Adding a new provider's MX records on top, without removing the old ones, leaves two competing sets of instructions in place, and different mail servers across the internet may honor either one inconsistently depending on caching and priority values.

How to Fix It

1. Log into your DNS panel — this is managed wherever your domain's DNS is hosted, which may be your registrar or a separate DNS provider like Cloudflare.
2. Find every existing MX record for the domain and note them down before touching anything, in case you need to reference them.
3. Delete all existing MX records completely rather than editing them — a clean slate avoids priority conflicts between old and new entries.
4. Add the exact MX records your new provider specifies, matching priority values precisely as shown in their setup wizard. Don't reuse values from older tutorials, since these occasionally change.
5. Verify the records are live using dig or nslookup before assuming the setup wizard's verification failure was your fault rather than a propagation delay.
6. Wait for DNS propagation — this can take anywhere from a few minutes to several hours — then retry verification in the email platform's setup flow.
7. Send a test email from an external address once verification succeeds, to confirm mail is actually routing correctly end to end, not just passing the platform's automated check.

Avoiding This When You Switch Providers Again Later

Whenever you change email providers in the future, treat MX record cleanup as its own explicit step in the migration, not an afterthought once something breaks. It also helps to review your SPF, DKIM, and DMARC records at the same time, since these are commonly configured alongside MX records and are just as easy to leave outdated after a provider switch — outdated SPF records in particular can cause legitimate mail to be marked as spam even after MX routing itself is fixed. If you're setting up professional email on a domain for the first time rather than migrating, you can skip the cleanup step entirely and just follow the new provider's instructions directly, since there's nothing old to conflict with.

Never lose a domain again

Track every domain you own in one dashboard. Free for up to 15 domains.