Introduction

Google Workspace mail often breaks after a domain transfer because the registrar moved, but the working DNS zone did not move cleanly with it. The MX records may be missing, the domain may still point to old nameservers, or only part of the email-related DNS was recreated at the new provider. The website can still look normal while Gmail delivery fails. The safest fix is to verify delegation and the full mail DNS set together instead of checking only the MX entry in one control panel.

Symptoms

  • Google Workspace inboxes stop receiving mail after a registrar or domain transfer
  • Senders get delivery failures or timeouts for the domain
  • The admin console expects Google MX records, but live DNS answers show something else
  • Webmail still opens, but inbound mail does not arrive
  • The issue started after changing registrars, nameservers, or DNS hosting

Common Causes

  • The domain transfer changed nameservers or reset the live DNS zone
  • Google Workspace MX records were not recreated at the new DNS provider
  • The new zone is missing SPF, DKIM, or other supporting email records
  • Some resolvers still query the old nameservers while others use the new zone
  • DNS templates or default parking records replaced the intended Google mail settings

Step-by-Step Fix

  1. Confirm which nameservers the domain is actually delegated to now, because the active DNS host matters more than the screen where you expected to manage records.
  2. Query the authoritative nameservers directly and compare the live MX answers with Google's required Workspace MX records.
  3. Recreate the Google Workspace MX records exactly in the active DNS zone if any priorities, hostnames, or targets are missing.
  4. Check whether the new DNS host also needs SPF, DKIM, DMARC, autodiscover, or verification records restored after the transfer.
  5. Remove conflicting parking, forwarding, or legacy MX records that can keep mail from consistently reaching Google.
  6. Verify there is no split state where the registrar shows one zone but the domain still delegates to another provider's nameservers.
  7. Retest inbound delivery only after the authoritative DNS answers are correct, because admin-console screenshots do not prove the internet sees the same records.
  8. Monitor delivery reports, bounces, and Google Workspace admin alerts while propagation finishes across resolvers.
  9. Keep a full export of the working mail DNS zone before future transfers so the next registrar move does not interrupt Workspace mail.