Contents
4 sections · 3 min read
DNS panel showing conflicting MX records during Google Workspace email setup
Freelancers

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

A
Domain 360 Team
·July 26, 2026·3 min read

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.

Quick answer: MX record conflicts almost always come from leftover records from your old email provider — most DNS panels won't let two sets of MX records coexist cleanly. Deleting the old provider's MX records completely before adding the new ones resolves the conflict in nearly every case.

Why Do 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.

What If You're Not Sure Where Your DNS Is Managed?

This trips people up more often than the MX conflict itself. Your domain's DNS is not necessarily managed at the same place you registered the domain — it's common to register at one company and point the domain's nameservers at a completely different DNS provider (Cloudflare being the most common). Run a quick DNS lookup on your domain and check the NS records: whatever company those nameservers belong to is where you need to log in to edit MX records, regardless of who your registrar is. Editing MX records at your registrar when your actual DNS is hosted elsewhere will have no effect at all, which is a common reason people think their fix "isn't working."

How Do You Fix an MX Record Conflict?

  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.

How Do You Avoid This the Next Time You Switch Providers?

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.

Quick Answers

Can I just add the new MX records without deleting the old ones?
No — mail servers use MX record priority to decide where to route email, and having two providers' records active at once causes mail to bounce, get lost, or deliver inconsistently between the two systems.
How many MX records does Google Workspace or Microsoft 365 actually need?
Google Workspace typically requires just one MX record pointing to a Google mail server with a specific priority. Microsoft 365 usually requires one record pointing to a domain-specific address they provide during setup — check the exact current values in each platform's setup wizard rather than relying on older instructions.
Why does mail still bounce even after I fixed the MX records?
DNS changes take time to propagate, and mail servers elsewhere on the internet may have cached your old MX records for a period defined by their TTL. Give it a few hours before assuming the fix itself failed.
Should I keep my old email provider active during the switch?
Briefly, yes — many businesses keep the old provider reachable for a short overlap period so any in-flight emails aren't lost, then fully cancel it once the new provider is confirmed working end to end.

Never lose a domain again

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