- Google Mail MX Records + Email Routing in cPanel (Hosticko Setup Guide)
- When you should use this setup
- Step 1: Set Email Routing to “Remote Mail Exchanger” in cPanel
- Step 2: Update your MX records for Google Workspace
- Where to edit MX records (cPanel Zone Editor vs Registrar)
- Step 3: Add SPF, DKIM, and DMARC for best deliverability
- How to verify everything is working
- Common issues and quick fixes
- Related Hosticko Guides
- FAQs
Google Mail MX Records + Email Routing in cPanel (Hosticko Setup Guide) #
Google Mail MX records must be configured correctly if you want your domain email (example@yourdomain.com)
to work with Google Workspace / Gmail. This guide shows you how to set Email Routing in cPanel
and update MX records so all incoming mail is delivered to Google, cleanly and reliably.
When you should use this setup #
- You bought hosting from Hosticko, but you want email handled by Google Workspace (Gmail).
- You want to use Google’s inbox, spam filtering, and business email tools, while keeping your website on Hosticko.
- You need to prevent mail delivery issues caused by “split routing” (some mail going to hosting, some to Google).
Step 1: Set Email Routing to “Remote Mail Exchanger” in cPanel #
This tells the server: “Do not deliver mail locally, deliver it to the external mail provider (Google).”
- Log in to your cPanel.
- Open Email Routing (usually under the Email section).
- Select your domain from the dropdown.
- Choose Remote Mail Exchanger.
- Click Change / Save.
If you skip this step, your server may still try to accept mail locally, which can cause missing emails or delivery loops.
Step 2: Update your MX records for Google Workspace #
Next, you must point your domain’s MX records to Google’s mail servers so the internet knows where to deliver your email.
Remove any old/non-Google MX records first to avoid conflicts.
Option A: Google’s current recommended MX record (single record) #
Google supports a single MX record value for Google Workspace:
- Type: MX
- Name/Host: @ (or leave blank depending on DNS panel)
- Priority: 1
- Value/Destination: smtp.google.com
Option B: Legacy Google MX records (still supported) #
If your domain has been using Google Workspace since before 2023, you may see the older “ASPMX” style records.
They are still supported by Google. If your mail is working, you don’t have to change it.
Keep only one MX setup (either the single record or the legacy set). Don’t mix Google MX with hosting-provider MX records.
Where to edit MX records (cPanel Zone Editor vs Registrar) #
1) If your DNS is managed in cPanel (common when you use your hosting nameservers) #
- Open cPanel → Zone Editor.
- Click Manage next to your domain.
- Locate existing MX records and remove the non-Google entries.
- Add the Google MX record(s) from the section above.
- Save changes.
2) If your DNS is managed at your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.) #
- Log in to your domain registrar/DNS provider dashboard.
- Open your domain’s DNS / Advanced DNS settings.
- Remove old/non-Google MX records.
- Add Google’s MX record(s) and save.
DNS updates can take time to propagate across the internet (often fast, but it can take up to 72 hours in some cases).
Step 3: Add SPF, DKIM, and DMARC for best deliverability #
MX records handle incoming mail, but SPF/DKIM/DMARC protect your domain and improve inbox placement for outgoing mail.
Google recommends setting these up to reduce spam issues and spoofing.
SPF (recommended) #
If you only send mail using Google Workspace, Google’s SPF example is:
v=spf1 include:_spf.google.com ~all
DKIM (recommended) #
DKIM is generated in the Google Admin Console, then published as a DNS TXT record. After publishing the record,
you enable DKIM signing in Google to start signing outgoing mail.
DMARC (highly recommended) #
DMARC is a DNS TXT record (usually at _dmarc.yourdomain.com) that tells receivers what to do if SPF/DKIM fail.
Start in “monitor mode” first (policy p=none) before enforcing stricter policies.
How to verify everything is working #
- Send a test email from a Gmail address to your domain email (example@yourdomain.com).
- Send a test email from your domain email to an external address (like Gmail).
- In Google Admin Toolbox (Dig), check the published MX records for your domain (advanced check).
If incoming mail still lands on the server instead of Gmail, it usually means either (1) MX records are still wrong, or
(2) Email Routing in cPanel is not set to Remote Mail Exchanger.
Common issues and quick fixes #
Emails are bouncing / not arriving #
- Double-check there are no old MX records left (non-Google entries often break delivery).
- Make sure your MX host/name is correct (often @ / blank).
- Wait for DNS propagation (can be up to 72 hours in edge cases).
Outgoing emails go to spam #
- Make sure SPF is present and correct.
- Enable DKIM signing in Google Admin Console after publishing the DKIM record.
- Add a DMARC record and start with monitoring policy.
FAQs #
Do I really need to change Email Routing in cPanel? #
Yes, if your website is hosted on Hosticko but email is on Google, set routing to Remote Mail Exchanger
to prevent the server from trying to handle mail locally.
Should I use Google’s single MX record or the legacy ASPMX records? #
Either works. If you’re setting up fresh, the single record is simple. If you already have legacy MX records and mail works,
you can keep them, just don’t mix them with non-Google MX records.
How long do MX record changes take? #
Often within minutes to a few hours, but DNS propagation can take up to 72 hours in some cases.
