How To Use Google Workspace Email With cPanel Hosting
This guide explains how to use Google Workspace email when your website is hosted in cPanel.
Simple Answer
If your domain email is using Google Workspace, your DNS email records must follow Google Workspace instructions. cPanel can still host your website, but your email must be routed to Google.
Important Note
Do not create or use cPanel email accounts if your domain email is already using Google Workspace. Your mailbox should be created and managed inside Google Workspace.
Before You Start
First, check where your domain DNS is currently managed.
If your domain nameservers are using iCoreHosting or cPanel nameservers, update the DNS records inside cPanel Zone Editor.
If your domain nameservers are using Cloudflare, Google Domains, Namecheap, GoDaddy, or another DNS provider, update the DNS records at that provider instead. Updating DNS inside cPanel will not work if cPanel is not the active DNS provider.
Required Google Workspace MX Record
In your DNS manager, remove old MX records that are not used anymore. Then add the Google Workspace MX record below.
| Record Type | MX |
| Name or Host | @ |
| Priority | 1 |
| Destination | smtp.google.com |
| TTL | Default value |
Important Note
Some DNS systems may require the destination to be entered as smtp.google.com. with a dot at the end. Please follow the format required by your DNS provider.
cPanel Email Routing Setting
After changing your MX record to Google Workspace, log in to cPanel and go to Email Routing.
Select your domain and choose Remote Mail Exchanger.
This tells cPanel that your domain email is handled by Google Workspace and not by the local cPanel mail server.
Important Note
If Email Routing is set wrongly, emails sent from your website or from the same server may try to deliver locally inside cPanel instead of going to Google Workspace.
SPF Record
SPF helps receiving mail servers know which servers are allowed to send email for your domain.
For Google Workspace only, the SPF record is usually:
v=spf1 include:_spf.google.com ~all
Only one SPF TXT record should exist for one domain. If your domain already has an SPF record, do not create another SPF record. You must update the existing SPF record.
DKIM Record
DKIM should be generated from your Google Admin Console.
After Google provides the DKIM TXT record, add it into your DNS manager. Then return to Google Admin Console and start authentication.
Do not copy DKIM records from another domain. Every domain has its own DKIM record.
DMARC Record
DMARC works together with SPF and DKIM. It helps protect your domain from email spoofing and improves email trust.
A basic starter DMARC record can be:
v=DMARC1; p=none; rua=mailto:[email protected]
Replace [email protected] with your own monitoring email address.
Common Mistakes
The most common mistake is updating DNS in cPanel while the domain is actually using Cloudflare or another DNS provider.
Another common mistake is keeping old MX records together with Google Workspace MX records.
Some users also forget to change cPanel Email Routing to Remote Mail Exchanger.
Some users create more than one SPF TXT record. This can cause SPF failure.
When To Contact Support
Contact iCoreHosting support if you are not sure where your DNS is hosted.
Contact iCoreHosting support if your email is not receiving after changing the MX record.
Contact iCoreHosting support if Google Admin Console still cannot verify your MX, SPF, DKIM, or DMARC record after DNS propagation.
Summary
When using Google Workspace email with cPanel hosting, cPanel can continue to host your website, but your email DNS must follow Google Workspace instructions.
Correct setup requires Google Workspace MX record, correct cPanel Email Routing, SPF, DKIM, and DMARC.
