Google Workspace MX Records Setup: Complete Step-by-Step Guide

Getting Google Workspace email working hinges entirely on one thing: having the right MX records pointed at Google's mail servers. Get them wrong and your mail either bounces, disappears into the void, or keeps routing to your old provider while you scratch your head wondering why nobody is receiving anything. This guide cuts straight to the fix, covering exactly which records to add, how to add them in the most common hosting control panels, and how to confirm everything is working before you close the browser tab.

What Are MX Records and Why Do They Matter for Google Workspace

An MX (Mail Exchanger) record is a DNS entry that tells the internet which mail servers are responsible for accepting email for your domain. When someone sends a message to you@yourdomain.com, their mail server queries DNS for your domain's MX records, then delivers the message to whichever server those records point to.

Without the correct MX records, Google's servers never receive your inbound email. Google Workspace provides five MX record entries, each with a different priority number. The priority number tells sending servers which host to try first — lower numbers get attempted before higher ones. All five records ultimately deliver to Google's infrastructure, but having multiple entries provides redundancy if one endpoint is temporarily unreachable.

The Exact MX Records Google Requires

These are the five MX records you must add for every domain using Google Workspace. The values are the same regardless of your registrar or hosting provider:

The Name or Host field for each record should be set to @ (which represents your root domain) or left blank, depending on your DNS provider's interface. The TTL can be left at the default, though setting it to 3600 (one hour) is reasonable.

Before You Start: Delete Your Old MX Records

This step trips up more people than anything else. If your domain previously had email hosted with your web host, a previous Google Workspace account, or any other provider, there are already MX records in your DNS zone. You must delete all existing MX records before or immediately after adding Google's records. Leaving old MX records in place creates split delivery — some messages will hit Google, others will hit your old host, and users will have inconsistent experience with mail appearing in different places.

Log into your DNS management interface, navigate to your MX records, write down what is currently there, then delete every existing entry before proceeding with the steps below.

Adding Google Workspace MX Records by Hosting Provider

GoDaddy

1. Log in at godaddy.com and go to My Products.
2. Find your domain and click DNS next to it.
3. Scroll to the MX section. Click the pencil icon to edit existing records and delete them, or use the Add button to create new ones.
4. For each record: set Host to @, enter the mail server hostname in the Points to field, enter the priority number in Priority, and set TTL to 1 hour.
5. Click Save after each entry, or add all five and save once if your interface supports bulk editing.

Namecheap

1. Log in and go to Domain List. Click Manage next to your domain.
2. Click the Advanced DNS tab.
3. Scroll to Mail Settings. Change the dropdown from Namecheap Web Hosting Email or Email Forwarding to Custom MX. This is critical — without switching to Custom MX, your additions won't take effect properly.
4. Delete any pre-existing MX entries shown.
5. Click Add New Record, select MX Record, set Host to @, enter the mail server value, enter priority, and save.

Cloudflare

1. Log in at cloudflare.com and select your domain.
2. Click DNS in the left sidebar, then Records.
3. Delete any existing MX records by clicking Edit then Delete.
4. Click Add record. Set type to MX, Name to @, Mail server to the Google hostname, and Priority to the correct value.
5. The Proxy status toggle does not apply to MX records — they are always DNS only.
6. Click Save. Repeat for all five records.

Bluehost

1. Log into your Bluehost account. Go to Domains, select your domain, and click Manage.
2. Open the DNS tab and scroll to the MX (Mail Exchanger) section.
3. Remove any existing MX records first.
4. Click Add Record. Enter @ in the Host field, the Google mail server hostname in the Points To field, and the priority value. Click Save.

SiteGround

1. Go to Site Tools for your site, then navigate to Domain and DNS Zone Editor.
2. Filter by type MX and delete all existing entries.
3. Click Create New Record, select MX, set the Name to your domain (or leave blank), enter the mail server and priority, then click Create.

cPanel (Generic)

Many shared hosts use cPanel. The process is similar across all of them:

1. In cPanel, scroll to the Email section and click MX Entry.
2. Set email routing to Remote Mail Exchanger. This tells cPanel not to try to handle mail locally.
3. Delete existing MX entries shown at the bottom.
4. In the Add New Record form, enter the priority and the destination (Google's hostname), then click Add New Record.

Verifying Your MX Records from the Command Line

Once you have added your records, do not just trust the control panel interface. Verify from the outside using command-line tools. Open Terminal (Mac/Linux) or Command Prompt / PowerShell (Windows) and run:

The output should list all five Google mail servers. A correct response looks like this:

If you still see your old provider's mail servers, propagation has not completed yet, or you made an error in the control panel. Double-check your entries and wait longer if needed.

You can also use the DNS Lookup tool to query your MX records from multiple global resolvers at once without touching the command line.

Verifying Inside Google Workspace Admin Console

Google Workspace includes its own MX verification step in the setup wizard, and you can also trigger it manually at any time:

1. Go to admin.google.com and sign in as the super administrator.
2. Navigate to Apps then Google Workspace then Gmail.
3. Scroll down to Authenticate email or look for a banner indicating that MX records are not set up yet.
4. Click Check MX records. Google will query your DNS and confirm whether the records are correctly configured.

If Google reports a problem but your command-line check shows the right records, you are likely still within the propagation window. Wait an hour and check again. If propagation is confirmed via external tools but Google still reports failure, log out and back in to the admin console, as it sometimes caches the previous negative result.

Common Mistakes and How to Avoid Them

• Not deleting old MX records: The most common problem. Always remove pre-existing entries before adding Google's.
• Adding a trailing dot incorrectly: Some DNS interfaces require a trailing period on hostnames (ASPMX.L.GOOGLE.COM.) while others handle it automatically. If your provider shows a validation error, try removing the trailing dot.
• Entering the priority in the wrong field: Some interfaces label priority as "preference" or ask for it in a combined field like "10 ASPMX.L.GOOGLE.COM". Read the field labels carefully.
• Leaving cPanel email routing on local: If your host uses cPanel and the routing is set to "Local Mail Exchanger," cPanel will intercept mail before it ever reaches Google. Set routing to "Remote Mail Exchanger."
• Setting up MX before Google verifies domain ownership: Google requires you to verify ownership of your domain before email begins flowing. If you have not completed verification, do that first through Google Workspace Admin Console using either a TXT record, CNAME record, or HTML file upload. MX records alone do not confirm ownership.
• Duplicate priority values causing confusion: Having ALT1 and ALT2 both at priority 5 is intentional and correct per Google's specification. Do not change these values to make them unique.

Setting Up SPF, DKIM, and DMARC After MX Records

Correct MX records get mail delivered to you. But to ensure mail sent from your Google Workspace account actually reaches recipients without landing in spam, you also need three additional DNS records:

• SPF (TXT record): Tells receiving servers that Google is authorized to send on behalf of your domain.
• DKIM (TXT record): A cryptographic signature Google generates to prove messages weren't forged in transit.
• DMARC (TXT record): A policy record that instructs receiving servers what to do when SPF or DKIM checks fail.

The minimum SPF record for Google Workspace looks like this:

For DKIM, go to Google Workspace Admin Console, then Apps, Google Workspace, Gmail, and click Authenticate email. Generate a DKIM key, copy the TXT record value, and add it to your DNS with the name Google specifies (usually something like google._domainkey).

DMARC is a separate TXT record on the _dmarc subdomain. A safe starting policy is:

Start with p=none to collect reports without affecting delivery, then move to p=quarantine or p=reject once you have confirmed all legitimate sending sources are covered by your SPF and DKIM records.

How Long Until Email Starts Working

Once your MX records are correctly saved in DNS, new inbound emails will start routing to Google Workspace as soon as the updated records propagate to the resolvers being used by sending mail servers. In practice, if your old TTL was 3600 seconds (one hour) or less, you will typically see mail flowing within 15 to 60 minutes. If your old TTL was 86400 (24 hours), you may need to wait up to 24 hours before all senders are using the updated records.

Mail sent during the transition period is not lost — sending servers queue messages and retry delivery for up to 72 hours, so once propagation is complete, any queued messages will be delivered automatically.

Testing Inbound Mail Delivery

After propagation looks good, send a test email from an external account (Gmail, Outlook, Yahoo — anything outside your domain) to a Google Workspace mailbox. Log into your Google Workspace account at mail.google.com and confirm the message arrives in the inbox. If it does, your setup is complete.

For a more detailed diagnostic, open the received message in Gmail, click the three-dot menu in the top right, and select Show original. Look at the Received headers — the last hop before delivery should show a Google infrastructure server (something ending in google.com), confirming the message traversed Google's mail handling system.