Gmail MX Records: What to Use and How to Verify

Google updated the Google Workspace MX record setup in 2023, simplifying from five records to a single MX record. Both setups still work, but the single-record format is the current default and the one you should use for new domains. This guide covers both, plus the verification steps and common configuration mistakes.

The modern Google Workspace MX setup

For any new Google Workspace domain configured after late 2023:

example.com.    MX    1    smtp.google.com.

That's it — one record at the root of your domain, priority 1, value smtp.google.com.

This is functionally equivalent to the legacy 5-record setup. Google handles the redundancy and load distribution behind the single hostname.

The legacy 5-record setup

Older Google Workspace domains use:

example.com.    MX    1    aspmx.l.google.com.
example.com.    MX    5    alt1.aspmx.l.google.com.
example.com.    MX    5    alt2.aspmx.l.google.com.
example.com.    MX   10    alt3.aspmx.l.google.com.
example.com.    MX   10    alt4.aspmx.l.google.com.

Five records, four priorities (the alt1/alt2 share priority 5, alt3/alt4 share priority 10). Lower priority = preferred.

If you already have this configuration, you can leave it — Google still accepts mail at these hostnames. You can also migrate to the single-record setup at any time.

How to add MX records

The process is similar at most DNS providers:

1. Log into your DNS provider's control panel (Cloudflare, GoDaddy, Google Domains, AWS Route 53, etc.)
2. Navigate to the DNS records for your domain
3. Add a new MX record:
   • Type: MX
   • Host/Name: @ or leave blank (means root of domain)
   • Priority: 1
   • Value/Points to: smtp.google.com
   • TTL: 3600 (1 hour) or your provider's default
4. Save

If you're replacing existing MX records (for example, switching from another provider to Google Workspace), delete the old records first. Multiple MX setups can cause unpredictable routing.

DNS provider quirks

Provider	Note
Cloudflare	Use the DNS tab. Make sure proxy is OFF for MX records (set to DNS Only).
GoDaddy	Use Domain Manager → DNS. Email Forwarding setting separate from MX.
AWS Route 53	Create record set with type MX. Value format: 1 smtp.google.com. (priority before hostname).
Cloudflare Registrar	Same as Cloudflare DNS — proxy off for MX.
Namecheap	Use Advanced DNS tab. "Mail Settings" must be set to Custom MX.
Google Domains	Use DNS → Custom Records. (Service discontinued; domain management moved to Squarespace.)

Verifying MX records

After adding, verify three ways:

1. dig from command line:

dig MX example.com +short
1 smtp.google.com.

2. Google Admin Toolbox CheckMX:

Visit toolbox.googleapps.com/apps/checkmx and enter your domain. The tool confirms Google Workspace MX configuration plus tests connectivity.

3. Google Admin Console:

In Google Workspace Admin Console → Apps → Google Workspace → Gmail → Setup, MX status appears with a verification indicator.

4. Send a test message:

Send mail to a Google Workspace user at your domain from an external account (your personal Gmail, for example). If it arrives, MX is working.

What MX records do not control

A frequent confusion: MX records affect inbound mail only, not outbound.

• MX records — where other servers should deliver mail addressed TO your domain
• SPF — which servers may send mail AS your domain (outbound authorization)
• DKIM — cryptographic signing of outbound mail
• DMARC — policy for receivers when outbound auth fails

You can configure outbound sending through Google Workspace without changing MX records — that's controlled by SMTP authentication (smtp.gmail.com or smtp-relay.gmail.com). MX only matters for receiving.

For the full set of email DNS records, see DNS records for email.

Common MX mistakes

Multiple MX setups conflicting. Old MX records from a previous provider not deleted, leaving both pointing at different services. Mail routing becomes unpredictable.

Trailing dot inconsistency. Some DNS UIs require the trailing dot (smtp.google.com.), some don't. If your provider rejects the value with a trailing dot, omit it. The actual stored record is identical either way.

Priority direction confusion. Lower priority number = higher preference. Setting priority 100 for smtp.google.com and priority 1 for an old mail server means the old server is preferred. Use priority 1 for the active mail provider.

Cloudflare proxy enabled on MX. Cloudflare's orange-cloud proxy doesn't work for MX records (it's HTTP only). Always set MX records to DNS Only (gray cloud).

MX pointing to a CNAME. RFC 2181 says MX records must point to an A or AAAA record, not a CNAME. Some setups work anyway, but it's non-standard and some receivers reject mail.

Trying to use MX records for outbound sending. MX records are inbound-only. SPF and DKIM control outbound.

Practitioner note: Before changing MX records on a domain with active mail flow, take a snapshot of the current records and time the cutover for low-volume hours. Inbound mail during the propagation window can deliver to either old or new servers, causing some messages to land in a mailbox you've already migrated away from.

Personal Gmail vs Google Workspace

Personal Gmail accounts (@gmail.com addresses) do not use custom domain MX records. You can only configure MX for a custom domain through Google Workspace (business plans starting at $7/user/month).

If you want a custom domain like [email protected] routed to a Gmail-like interface but don't want to pay for Workspace, alternatives include:

• Zoho Mail (free for up to 5 users on one domain)
• Proton Mail
• Fastmail
• Cloudflare Email Routing (forwards to existing mailbox, no full mailbox hosting)

Migrating to Google Workspace

When moving an existing mail setup to Google Workspace:

1. Set up Google Workspace, verify the domain (TXT record), and add users
2. Pre-populate mailboxes via IMAP migration from the old system
3. Schedule MX cutover for low-volume time
4. Change MX records to smtp.google.com (priority 1)
5. Set old MX TTL to 300 (5 minutes) 24+ hours before cutover for faster propagation
6. After 4 to 24 hours, decommission old mail server

See Google's MX records setup guide for step-by-step migration.

Mail routing for subdomains

Subdomains do not inherit MX records from the parent domain. If you need mail for staff.example.com, publish MX records on the subdomain itself:

staff.example.com.    MX    1    smtp.google.com.

If you only have MX on the root, mail to [email protected] will not deliver via Google Workspace.

Practitioner note: A common consultancy finding is missing subdomain MX records — the marketing team set up "campaigns.example.com" but never added MX, so replies vanish. Audit MX coverage across all sending subdomains, even ones you only use for outbound.

If you're migrating to Google Workspace or troubleshooting an MX configuration issue, book a consultation. Mail routing changes are common engagement type and getting the cutover right matters.

Sources

• Google — Set up MX Records for Google Workspace Gmail
• Google — Modernize Your MX Records
• Google Admin Toolbox — CheckMX
• RFC 5321: Simple Mail Transfer Protocol — MX behavior
• RFC 2181: Clarifications to the DNS Specification
• Cloudflare — Add Google MX Records

---

v1.0 · May 2026