This guide walks you through adding Google Workspace (formerly G Suite) MX records in cPanel to route your domain's email to Google.
Before You Begin
- You need an active Google Workspace account with your domain added.
- You must have access to your cPanel account.
- Removing old MX records will temporarily disrupt email delivery until the new ones propagate.
Step 1: Remove Existing MX Records
1. Log in to your cPanel account.
2. In the Domains section, click on Zone Editor.
3. Click Manage next to your domain.
4. Use the Filter dropdown to show only MX records.
5. Delete any existing MX records to avoid conflicts.
Step 2: Add Google MX Records
Click Add Record and add each of the following five MX records:
| Priority | Destination |
|---|---|
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 |
For each record: set Type to MX, enter the destination, and set the priority as shown. The trailing dot (.) on the destination is handled automatically by cPanel — do not add it manually.
Step 3: Change Email Routing
1. Return to the cPanel home.
2. In the Email section, click Email Routing.
3. Select Remote Mail Exchanger and click Change.
This tells your server to deliver incoming email to Google's servers instead of handling it locally.
Step 4: Verify in Google Workspace
1. Go to the Google Workspace Admin Console.
2. Navigate to Account → Domains → Manage domains.
3. Click Verify domain or check the status of your MX records.
Important Notes
- DNS changes (including MX records) can take up to 48 hours to propagate worldwide, though most updates complete within a few hours.
- Do not delete your cPanel email accounts until Google Workspace is fully working, so you can access old messages.
- If you have a website on this domain, MX changes will not affect your website — only email routing is changed.
Troubleshooting
- Email not receiving after 48 hours: Verify the MX records using a tool like Google's DIG tool or MXToolbox.
- "Local Mail Exchanger" conflict: Make sure you completed Step 3 and changed email routing to Remote.
- Missing SPF record: Google recommends also adding an SPF record. Add a
TXTrecord with valuev=spf1 include:_spf.google.com ~all.
