How to Set Up MX Records for Google Workspace in 2026

Setting up MX records for Google Workspace is one of the first DNS tasks for any new sending domain — and one of the most common to get slightly wrong. Google’s documentation is good but split across multiple pages; this guide consolidates the steps, the exact values, and the verification process into one walkthrough. It pairs with the what are MX records guide and the email deliverability guide.

Google Workspace MX setup in 2026 uses a single MX record pointing to smtp.google.com with priority 1. This is a change from the older five-record Google MX setup (with aspmx.l.google.com and four fallback servers). Google migrated to the simplified record in 2023, and new domains should use the new format.

The MX record values

The current Google Workspace MX configuration is:

Priority	Hostname
1	smtp.google.com

That’s it. One record.

If you’re migrating an existing setup that still has the old five-record configuration, you can leave it or migrate to the new format. Both work; the new format is recommended for new setups.

The old format (still supported but not recommended for new setups):

Priority	Hostname
1	aspmx.l.google.com
5	alt1.aspmx.l.google.com
5	alt2.aspmx.l.google.com
10	alt3.aspmx.l.google.com
10	alt4.aspmx.l.google.com

If you see the old format in an existing setup, it’s fine. Don’t change it unless you have a specific reason.

Step-by-step setup

Step 1: Log into your DNS provider. Whoever manages DNS for your domain — Cloudflare, AWS Route53, GoDaddy, Namecheap, Hover, the registrar’s default DNS panel. The exact UI varies, but the steps are similar.

Step 2: Navigate to DNS records for your domain. Look for “DNS Management,” “Manage DNS,” “DNS Settings,” or similar. You should see a list of current records (A, CNAME, TXT, MX, etc.).

Step 3: Remove any existing MX records. If you’re migrating from another email provider (or had a placeholder MX setup), delete the old records first. Don’t mix old and new MX entries — receiving systems will use whatever returns first and the routing becomes unpredictable.

Step 4: Add the new MX record. Create a new record with:

• Type: MX
• Host/Name: @ (or leave blank, depending on provider — represents the root domain)
• Value/Mail Server: smtp.google.com
• Priority: 1
• TTL: Default (typically 3600 or 14400)

Save the record.

Step 5: Wait for propagation. DNS changes propagate in 5 minutes to 24 hours depending on TTL and DNS provider. Most modern providers (Cloudflare, AWS) propagate in seconds; older registrars can take an hour or more.

Step 6: Verify the MX record is correct. Use dig +short MX yourdomain.com from a terminal, or use MXToolbox’s MX Lookup tool. You should see exactly one MX record pointing to smtp.google.com with priority 1.

Step 7: Verify in Google Workspace Admin Console. Log into Admin Console at admin.google.com → Apps → Google Workspace → Gmail → “Verify your domain.” Google’s tool will check that the MX record is in place and active. Once verified, mail delivery to Google Workspace is operational.

DNS provider quick reference

The exact UI varies but key concepts are consistent.

Cloudflare: DNS → Records → Add Record → Type: MX, Name: @, Mail server: smtp.google.com, Priority: 1.

AWS Route53: Hosted Zones → Select your domain → Create Record → Type: MX, Value: 1 smtp.google.com, TTL: 300.

GoDaddy: My Domains → Manage DNS → Add (under Records) → Type: MX, Host: @, Points to: smtp.google.com, Priority: 1.

Namecheap: Domain List → Manage → Advanced DNS → Add New Record → Type: MX Record, Host: @, Value: smtp.google.com, Priority: 1.

Hover: DNS → Add Record → Type: MX, Host: @, Value: smtp.google.com, Priority: 1.

Google Domains (now Squarespace Domains): Mail → MX records → Use custom MX records → Priority: 1, Server: smtp.google.com.

For other providers, the pattern is consistent: find DNS records, add MX type, hostname is @ (root), value is smtp.google.com, priority is 1.

Common mistakes

Keeping old MX records alongside the new one. Both old and new will resolve, but receiving systems may use the old format inconsistently. Always remove old records before adding the new format.

Using smtp.google.com as the host name instead of the mail server value. The host name (@ or your domain) is where the MX record sits in DNS. The value (smtp.google.com) is where mail gets routed. Swapping these breaks everything.

Missing the priority value. Most DNS providers require a priority; some default it to 0 or 10 if not specified, which doesn’t match Google’s expected priority of 1. Always set priority explicitly.

Adding the record without removing placeholder records. Some DNS providers add default MX records (e.g., the registrar’s email forwarding). These should be removed when migrating to Google Workspace.

Not waiting for propagation before verifying in Admin Console. Google’s verification tool checks DNS in real-time. If you check before propagation completes, it’ll show “MX record not found” even when the record is configured. Wait 15-60 minutes before initial verification.

Setting up MX records for the wrong domain. If you have multiple domains (yourdomain.com, yourdomain.co, outreach.yourdomain.com), each needs its own MX record set if it should receive mail. Confirm which domain you’re configuring before adding records.

The Google Workspace MX setup is straightforward but worth getting right the first time. Misconfigured MX records produce silent reply-loss; correctly configured ones just work and don’t require thinking about again until the next infrastructure change.