MailFixIt

Google Workspace email configuration guide

Google Workspace: MX records not receiving mail

Mail for the domain is not reaching Google Workspace, either because the public MX route is wrong or the destination account is not ready for the recipient.

Problem description

A provider setup symptom may look like:

MX records not receiving mail after a provider DNS change.

Check the sending domain

What this usually means

Mail for the domain is not reaching Google Workspace, either because the public MX route is wrong or the destination account is not ready for the recipient.

Fix it

  1. In the Google Admin console, verify the domain and create users or aliases before moving delivery. Use the MX values Google currently shows for your account; older and newer Workspace setups may display different supported record sets.
  2. Confirm that the domain is accepted and every required mailbox or alias exists before changing MX.
  3. Publish the complete MX set for that exact domain in the authoritative DNS zone.
  4. Remove obsolete MX records only for direct delivery. If a security gateway intentionally receives first, keep it public and correct its next hop to Google Workspace.
  5. After cache expiry, check the public MX answer and send a new message to an existing recipient.

Common mistake

MX selects where incoming mail goes; it does not create or license a mailbox. Mixing unrelated provider MX records can send different deliveries to different systems.

What MailFixIt can check

MailFixIt can expose missing, conflicting, or invalid public MX records. It cannot activate a Google Workspace account or create a mailbox.

Use the related guides for the exact DNS or authentication warning, then test the same mail path again.

Frequently asked questions

What does MailFixIt check for Google Workspace?

It checks the public MX route and visible conflicts. The provider console must confirm account readiness, and a new delivery or message header must confirm the result.

Should I replace every existing DNS record with the provider values?

No. Confirm the exact record type and owner, preserve unrelated legitimate services, and change only the provider-controlled record required for the intended mail route.

Related email diagnostics

Email delivery delayed or rejected after a DNS migrationDiagnose email that stopped arriving after a DNS change. Compare public MX records with the intended provider and avoid false alarms for mail gateways. SPF is not configured for the envelope sender domainDiagnose SPF missing on a bounce or MAIL FROM subdomain. Check the exact envelope domain, add only authorized senders, and verify safely. DKIM public key record is invalid or revokedDiagnose an invalid or revoked DKIM public key record. Check the exact DKIM selector in public DNS before replacing a sender-provided key.

Primary sources: Google Workspace MX setup.