Google MX Records: Complete Setup Guide for Google Workspace

Google Workspace (formerly G Suite) is one of the most popular email solutions for businesses. Setting up MX records correctly is essential for routing email through Gmail's servers.

This guide covers the exact MX records you need, how to add them to your DNS provider, and how to verify everything is working.

Google Workspace MX Records

Google provides five MX records for redundancy and load balancing. Here are the current values:

The primary server (aspmx.l.google.com) has priority 1. Two alternates share priority 5, and two more share priority 10. This creates three tiers of redundancy.

Adding Google MX Records to Your DNS

The process varies by DNS provider, but the general steps are the same:

Step 1: Access your DNS settings. Log into your domain registrar or DNS provider. Find the DNS management or zone editor section.

Step 2: Remove existing MX records. Delete any MX records currently configured for your domain. Old records can conflict with Google's servers.

Step 3: Add each Google MX record. Create five new MX records, one for each server listed above. Enter the priority and mail server hostname exactly as shown.

Step 4: Save your changes. Apply the DNS changes. Some providers have a separate publish or save button.

Step 5: Wait for propagation. DNS changes can take up to 48 hours to fully propagate, though most take effect within a few hours.

Priority Settings Explained

Google's priority structure ensures reliable email delivery:

Priority 1 (aspmx.l.google.com): The primary server. All email attempts delivery here first.

Priority 5 (alt1 and alt2): First-level backups. If the primary is unavailable, email routes to one of these servers randomly (since they share the same priority).

Priority 10 (alt3 and alt4): Second-level backups. These handle email only when priority 1 and 5 servers are all unreachable.

This redundant structure means Google Workspace email is extremely reliable. Multiple servers would need to fail simultaneously for email delivery to be affected.

Common Mistakes When Setting Up Google MX

Several errors frequently cause Google Workspace email problems:

Using incorrect hostnames. The servers must be spelled exactly right. Common typos include forgetting the "l" in aspmx.l.google.com or adding extra characters.

Wrong priority values. Using priorities like 10, 20, 30 instead of Google's recommended 1, 5, 5, 10, 10 can work, but may not route traffic optimally.

Leaving old MX records. If you're migrating from another email provider, their MX records might still exist. Email could route to the old provider instead of Google.

Adding MX records for a subdomain. Google Workspace MX records should be set at your root domain (example.com), not a subdomain like mail.example.com.

Forgetting to verify the domain. Google requires domain verification before email works. MX records alone aren't enough—you also need the TXT verification record.

Verifying Your Google MX Configuration

After adding MX records, verify they're working:

Use our MX lookup tool to see what MX records are published for your domain. All five Google servers should appear with correct priorities.

Send a test email from an external account (like a personal Gmail or Outlook) to your Google Workspace address. If it arrives, your MX records are working.

Check the Google Admin console. Google Workspace provides a setup wizard that checks your MX records and reports any issues.

Wait before troubleshooting. DNS propagation takes time. If records don't appear immediately, wait a few hours before assuming something is wrong.

Google MX Records vs Other Google DNS Records

MX records are just one part of setting up Google Workspace. You'll also need:

TXT record for domain verification. Google requires you to prove domain ownership before activating email. This is usually a TXT record with a unique verification code.

SPF record for email authentication. Tells receiving servers that Google is authorized to send email from your domain. The value is typically v=spf1 include:_spf.google.com ~all. Check yours at spfrecordcheck.com.

DKIM records for email signing. Google Workspace generates a unique DKIM key for your domain. You add this as a TXT record, and Google signs outgoing email. Verify your setup at dkimtest.com.

DMARC record for policy enforcement. Specifies how to handle email that fails authentication. Check your policy at dmarcrecordchecker.com.

Migrating to Google Workspace from Another Provider

When switching email providers, the MX record change is the critical moment. Here's how to do it smoothly:

Before the switch:

• Set up Google Workspace and verify your domain
• Create user accounts and configure settings
• Lower your MX record TTL to 300-600 seconds (a day or two before switching)
• Import existing email if needed using Google's migration tools

During the switch:

• Delete old MX records
• Add all five Google MX records
• Verify records appear correctly with an MX lookup

After the switch:

• Test sending and receiving from multiple external accounts
• Monitor for bounced emails or delivery issues
• Raise TTL back to normal (3600 seconds or higher) after confirming everything works
• Keep old email server running briefly in case of issues

Troubleshooting Google MX Issues

If email isn't working after setting up MX records:

Records not appearing in lookups. Wait for DNS propagation. If still missing after 48 hours, verify you're editing the correct DNS zone.

Email bouncing with "user unknown." MX records might be correct, but the user doesn't exist in Google Workspace. Check that the mailbox is created.

Email delivering to old provider. Old MX records may still exist, or your DNS changes haven't propagated. Check for any non-Google MX records.

Intermittent delivery. If some emails arrive and others don't, check that all five MX records are present with correct priorities.

"MX record points to a CNAME" error. Google MX hostnames resolve correctly, but your domain might have conflicting CNAME records.

Monitor Your MX Records

Checking once is good. Monitoring continuously is better. The Email Deliverability Suite watches your SPF, DKIM, DMARC, and MX records daily and alerts you when something breaks.