Google Workspace records at A2 Hosting
Google gives you each value in the Google Admin console. Add them in this order: verification first, the mail record and the Email Routing switch once the new mailboxes are ready, then the three records that keep your mail out of spam. In the table, example.com stands for your own domain.
| Record | Name | Value |
| Verify the domainTXT | example.com | google-site-verification= followed by your code from the Admin console |
| Receive mailMX, priority 1 | example.com | smtp.google.com |
| SPFTXT | example.com | v=spf1 include:_spf.google.com ~all |
| DKIMTXT | google._domainkey.example.com | The key starting v=DKIM1; that the Admin console generates for you |
| DMARCTXT | _dmarc.example.com | v=DMARC1; p=none; rua=mailto: followed by an address you read |
Verifying the domain
In the Admin console, go to Account, Domains, Manage domains, and select Verify domain. Copy the whole value, including google-site-verification=, and add it in the Zone Editor as a TXT record named with your domain. Leave it in place until Google confirms, which Google says can take up to 72 hours. This record proves you own the domain and does not change where your email goes, so it is safe to add while your cPanel email keeps working. If Google still refuses, the usual causes are in Google Workspace domain verification failed.
Pointing mail at Google
First delete the MX records already in the zone. Hosting.com's Google Workspace guide starts there, and Google says to remove any other MX records because leftovers can stop mail working. On a cPanel account the existing record usually points at your own hosting server at priority 0, which outranks Google's priority 1, so leaving it would keep mail flowing to the old mailboxes. Then add smtp.google.com at priority 1. Make this change only when the new mailboxes exist. If your Workspace account dates from before April 2023 and uses Google's older values that start with aspmx, and your mail works, nothing needs to change.
Switching Email Routing to Remote
This is a cPanel setting, not a DNS record. In cPanel, on the Tools page, in the Email section, select Email Routing, pick the domain, choose Remote Mail Exchanger and select Change (Hosting.com's Google Workspace guide). Hosting.com warns that if it is left on Local, the server delivers the domain's mail into a local mailbox that nobody reads, so that mail never reaches Google.
SPF, DKIM and DMARC
For SPF, Google's value when Workspace is your only sender is v=spf1 include:_spf.google.com ~all. If an SPF record already exists, edit it rather than adding a second, and put any other service that sends as you in the same record (Google's SPF guide). If the website on your A2 hosting also sends mail as your domain, such as a contact form, keep Hosting.com's include:spf.mysecurecloudhost.com in that one record beside Google's, which is the include Hosting.com lists for web hosting.
For DKIM, wait 24 to 72 hours after Gmail is turned on. Then, in the Admin console, go to Apps, Google Workspace, Gmail, Authenticate email, and generate a new record. Add it in the Zone Editor as a TXT record named google._domainkey.example.com, and only then select Start authentication (Google's DKIM guide).
Add DMARC last; Hosting.com notes that cPanel does not create it for you. Google suggests waiting 48 hours after SPF and DKIM, then starting at p=none, which only reports and blocks nothing, and tightening it once the reports show your real mail passing (Google's DMARC guide).