How to Configure MX Records for G Suite or Google Workspace

Google Workspace MX Record Values: The Exact Configuration You Need

To receive email for your custom domain using Google Workspace (formerly G Suite), you must add specific MX records to your domain's DNS settings. These records tell the world's email servers that Google's infrastructure is responsible for accepting and delivering email to your @yourdomain.com addresses.

Google provides five MX record entries for maximum redundancy and global coverage. Here are the exact values you need to configure:

Host/Name        | Priority | Mail Server Address
-----------------|----------|------------------------------
@ or yourdomain  | 1        | aspmx.l.google.com
@ or yourdomain  | 5        | alt1.aspmx.l.google.com
@ or yourdomain  | 5        | alt2.aspmx.l.google.com
@ or yourdomain  | 10       | alt3.aspmx.l.google.com
@ or yourdomain  | 10       | alt4.aspmx.l.google.com

What These Records Do

• Priority 1 (aspmx.l.google.com): Google's primary mail server. This is tried first for all email deliveries.
• Priority 5 (alt1 and alt2): Secondary servers used when the primary is unavailable. Two servers with the same priority provide load distribution.
• Priority 10 (alt3 and alt4): Tertiary backup servers used only if all higher-priority servers fail.

Google's global infrastructure is designed for 99.9%+ uptime. The multiple records protect against rare regional outages, network issues, and DDoS attacks.

Prerequisites: What You Need Before Configuring MX Records

Before touching your DNS settings, complete these prerequisite steps to ensure a smooth configuration.

1. Active Google Workspace Account

You must have an active Google Workspace subscription with your custom domain verified. If you haven't completed Google's domain verification (usually via TXT record or HTML file upload), do that first. Google provides step-by-step instructions during Workspace setup.

2. Access to Your DNS Management Panel

You need login credentials for wherever your domain's DNS is managed. Common DNS hosts include:

• Domain registrar (GoDaddy, Namecheap, Google Domains, Cloudflare Registrar)
• Web hosting provider (Bluehost, SiteGround, HostGator)
• DNS specialist (Cloudflare, AWS Route53, DNSimple)
• Your own DNS server (if self-hosting)

If you're unsure where your DNS is managed, use our DNS Lookup Tool to find your authoritative nameservers. The nameserver domain typically indicates your DNS provider.

3. Back Up Existing MX Records

Before making changes, document your current MX records. Take a screenshot or copy/paste into a text file. If something goes wrong, you can revert to the working configuration.

Use our MX Lookup Tool to query your current records before making changes. The tool shows exactly what external senders see.

4. Understand DNS Propagation

DNS changes don't take effect instantly. When you update MX records, the changes must propagate across thousands of DNS resolvers worldwide. This typically takes 5-30 minutes but can take up to 48 hours in rare cases. During propagation, some senders may see old records while others see new records.

Plan your migration during low-traffic periods and expect temporary inconsistency.

Step-by-Step Guide to Updating MX Records

Follow this general process, then refer to the provider-specific section below for exact screens and field names.

Step 1: Log Into Your DNS Provider

Navigate to your DNS management dashboard. Look for sections labeled "DNS Management," "DNS Settings," "Zone Editor," or "Domain Management."

Step 2: Locate Existing MX Records

Find the section displaying current MX records. You'll typically see a table with columns for Host/Name, Priority/Preference, and Value/Target/Exchange.

Step 3: Delete or Modify Existing MX Records

If you have existing MX records from a previous email provider, you need to remove them or change their priority to be higher than Google's (so Google is tried first). The safest approach is to delete all existing MX records and add Google's fresh.

Why delete? If you have multiple MX records from different providers, sending servers may deliver email to the wrong server based on priority. For example, if your old provider's MX has priority 10 and Google's has priority 20, email goes to the old provider first.

Step 4: Add Google Workspace MX Records

Add each of the five MX records listed above. For each record, specify:

• Host/Name: Usually @, blank, or your domain name
• Priority/Preference: 1, 5, 5, 10, 10 as shown
• Value/Target/Exchange: The Google mail server addresses exactly as written (including the trailing dots in some systems)

Step 5: Save and Verify

Click Save, Apply, or Update. Your DNS provider may show a confirmation message. Immediately use our MX Lookup Tool to verify the records are published. Initial queries may still show old records due to caching, but the tool should at least show the new records as well.

Configuration by DNS Provider: Exact Steps for Popular Services

DNS interfaces vary significantly. Here are step-by-step instructions for the most common providers.

Cloudflare

1. Log into Cloudflare dashboard.
2. Select your domain.
3. Click "DNS" in the top navigation.
4. Click "Add record."
5. Select "MX" from the type dropdown.
6. For each Google record:
   • Name: Leave blank or enter @ (for root domain)
   • Mail server: Enter the Google server address (e.g., aspmx.l.google.com)
   • Priority: Enter the priority number
   • TTL: Auto (or 3600 for 1 hour)
   • Click "Save"
7. Repeat for all five MX records.

GoDaddy

1. Log into GoDaddy Domain Control Center.
2. Select your domain.
3. Click "DNS" or "Manage DNS."
4. Scroll to "MX Records" section.
5. Delete any existing MX records (click three dots → Delete).
6. Click "Add" or "Add New Record."
7. Select "MX" from type dropdown.
8. For each record:
   • Host: @
   • Points to: Google server address
   • Priority: Enter priority number
   • TTL: 1 Hour
9. Click "Save" after each entry.

Namecheap

1. Log into Namecheap account.
2. Go to Domain List → Manage (next to your domain).
3. Click "Advanced DNS" tab.
4. Under "Mail Settings," select "Custom MX" from dropdown.
5. Delete any existing MX records.
6. Click "Add New Record" for each Google MX:
   • Priority: Enter priority number
   • Host: @
   • Value: Google server address
   • TTL: 1800 (30 minutes) or 3600 (1 hour)

AWS Route53

1. Log into AWS Console → Route53.
2. Select "Hosted zones" and click your domain.
3. Click "Create record."
4. Select "MX" as record type.
5. For "Value": Enter in format: 1 aspmx.l.google.com (priority followed by server)
6. Leave "Name" blank for root domain.
7. Click "Create records" to add all five at once using multi-value syntax.

Verifying Your Google Workspace MX Configuration

After adding MX records, you must verify they're working correctly before relying on them for business email.

Immediate Verification (DNS Propagation Check)

Use our MX Lookup Tool to query your domain's MX records:

1. Enter your domain name.
2. Click "Lookup."
3. Verify the returned records exactly match Google's five entries with correct priorities.

If the tool shows old records, wait 5-15 minutes and try again. DNS resolvers cache records, so it takes time for updates to appear.

Google Workspace Admin Console Verification

1. Log into Google Admin console (admin.google.com).
2. Go to Apps → Gmail → Default routing (or Hosts).
3. Look for MX record verification status. Google will show "Verified" once it detects the correct records.
4. If not verified, click "Verify MX records" to force a recheck.

Live Email Test

The ultimate verification: send test emails to your domain from external email addresses (Gmail, Outlook, Yahoo, etc.).

1. Create a test email address in Google Workspace (e.g., test@yourdomain.com).
2. Send emails from multiple external providers.
3. Check that emails arrive in your Google Workspace inbox.
4. Check that replies work correctly.

Monitor for 48 Hours

Due to DNS propagation delays, continue monitoring for 48 hours after initial configuration. Some senders (especially those with aggressive DNS caching) may still attempt delivery to old MX records during this window.

Troubleshooting Common Google Workspace MX Issues

Even with correct configuration, issues can arise. Here's how to diagnose and fix them.

Issue 1: "No MX Records Found" in MX Lookup Tool

Possible causes: Records haven't been added, saved incorrectly, or haven't propagated.

Solutions:

• Verify you clicked "Save" or "Apply" after adding records.
• Check that you're editing the correct domain (not a subdomain).
• Use a public DNS checker (like 8.8.8.8) to bypass your local DNS cache.
• Wait 30 minutes and check again (propagation takes time).

Issue 2: MX Records Point to Google but Email Goes Elsewhere

Possible causes: Conflicting records, cached DNS, or forwarding rules.

Solutions:

• Delete any non-Google MX records (they may have equal or lower priority).
• Check for email forwarding at your domain registrar (some offer free forwarding that bypasses MX).
• Verify your domain isn't using third-party email security gateways that intercept mail before Google.

Issue 3: Some Senders Get Bounce Messages

Possible causes: DNS propagation delay, sender DNS caching, or SPF/DKIM issues.

Solutions:

• Wait 24-48 hours for global propagation.
• Configure SPF record to authorize Google Workspace sending: v=spf1 include:_spf.google.com ~all
• Set up DKIM signing in Google Workspace Admin console.
• Configure DMARC to monitor authentication failures.

Issue 4: Google Admin Console Shows "Not Verified"

Possible causes: Google hasn't rechecked your DNS, or records are incorrect.

Solutions:

• Click "Verify MX records" button to force a recheck.
• Wait up to 72 hours (Google checks periodically).
• Verify exact spelling of server addresses (aspmx.l.google.com NOT aspmx.google.com).
• Check for trailing dots in DNS records (some providers require them).