Guide

A2 Hosting DNS for Google Workspace and Microsoft 365, record by record

A2 Hosting is now Hosting.com, and cPanel still holds your DNS. Here is where each record goes, the one cPanel setting that decides where mail lands, and the few mistakes that stop email working.

Facts checked

At A2 Hosting, now Hosting.com, every record for Google Workspace or Microsoft 365 goes in cPanel's Zone Editor: log in to cPanel, select Zone Editor in the Domains section, select Manage next to your domain, then pick the record type from the arrow beside Add Record. Type the full name, such as example.com or _dmarc.example.com, paste the value Google or Microsoft gave you, and save. One switch sits outside the Zone Editor: set Email Routing to Remote Mail Exchanger, or the hosting server can keep mail for your domain in a local mailbox nobody reads (Hosting.com's mail routing guide).

That only works when Hosting.com answers your domain's DNS. If your nameservers point at another company, such as your registrar or Cloudflare, records added in cPanel do nothing, and the records go at that company instead. Our free DNS lookup tells you which in a few seconds.

Adding a record at A2 Hosting

The same six steps for every record on this page. Only the type, the name and the value change.

  1. Check that Hosting.com answers your DNS.

    Run your domain through our DNS lookup and read the nameserver lines. Hosting.com's standard nameservers end in stableserver.net, and it notes that some older accounts use a different set, shown in its Hosting Panel. If yours name another company, add every record below at that company instead.

  2. Open the Zone Editor.

    Log in to cPanel. On the Tools page, in the Domains section, select Zone Editor, then select Manage next to the domain (Hosting.com's Zone Editor guide). A domain with no hosting plan works differently: one bought from Hosting.com on or after April 28, 2025 is managed in the Hosting Panel under DNS, and one bought from A2 before that date needs a support ticket.

  3. Pick the record type from Add Record.

    Select the down arrow next to Add Record, then TXT, MX or CNAME, whichever the tables below say.

  4. Type the full name, your domain included.

    Hosting.com's guide says to type the fully qualified name in the Name box: example.com for the main domain, _dmarc.example.com for DMARC, with your own domain in place of example.com. Hosts such as GoDaddy want @ instead; cPanel wants the whole name.

  5. Paste the value exactly and keep the TTL at 14400.

    Paste with no spaces or quote marks around it. Hosting.com suggests 14400 seconds (four hours) when unsure, and Microsoft says Exchange Online needs a TTL under six hours, which 14400 is.

  6. Save, then check it is public.

    Select the save button, named Add Record or Save Record depending on the screen. Then run the DNS lookup again: once the record shows there, Google and Microsoft can see it too.

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.

RecordNameValue
Verify the domainTXTexample.comgoogle-site-verification= followed by your code from the Admin console
Receive mailMX, priority 1example.comsmtp.google.com
SPFTXTexample.comv=spf1 include:_spf.google.com ~all
DKIMTXTgoogle._domainkey.example.comThe key starting v=DKIM1; that the Admin console generates for you
DMARCTXT_dmarc.example.comv=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).

Microsoft 365 records at A2 Hosting

Microsoft's list of host by host guides does not include A2 Hosting or Hosting.com, so the records below follow its guide for any DNS host. In the Microsoft 365 admin center, go to Settings, Domains, select your domain, then DNS records and Manage DNS, and select Continue. With Exchange and Exchange Online Protection selected, open the MX, CNAME and TXT lists to see the values for your domain. Microsoft adds records for you only at hosts that support Domain Connect; otherwise they go in by hand, with the six steps above.

RecordNameValue
Verify the domainTXTexample.comMS=ms followed by the number the admin center shows you
Receive mailMX, priority 0example.comYour domain's own address, copied from the admin center
Outlook setupCNAMEautodiscover.example.comautodiscover.outlook.com
SPFTXTexample.comv=spf1 include:spf.protection.outlook.com -all
DKIMCNAME, two recordsselector1._domainkey.example.com
selector2._domainkey.example.com
The two values the Microsoft Defender portal shows for your domain
DMARCTXT_dmarc.example.comv=DMARC1; p=none; rua=mailto: followed by an address you read

Microsoft says to add your users and mailboxes before you change the MX record, set its priority to the highest available, which is usually 0, and remove any MX record still pointing at the old email provider. On a cPanel account that is the record cPanel made for your hosting server.

Clearing cPanel's autodiscover record first

By default, cPanel creates its own autodiscover records, an A record at autodiscover.example.com and an SRV record beside it, so Outlook can find the mailboxes on the hosting server. A name that carries a CNAME cannot carry any other record, so delete cPanel's autodiscover A record in the Zone Editor before adding Microsoft's CNAME. Hosting.com says these records rarely cause trouble and can be deleted when they do.

Switching Email Routing to Remote

Microsoft 365 needs the same cPanel switch as Google. Under Email Routing, choose Remote Mail Exchanger for the domain; Hosting.com lists Microsoft 365 as a case for Remote, because on Local the server keeps the domain's mail for itself.

SPF, DKIM and DMARC

The SPF value above is Microsoft's for a domain that sends mail through Microsoft 365 only. Like Google, Microsoft allows one SPF record per domain, so edit an existing record rather than adding another, and keep include:spf.mysecurecloudhost.com in it if the website on your hosting still sends mail as your domain.

DKIM is turned on in the Microsoft Defender portal, under Email authentication settings, on the DKIM tab. Select your domain and Create DKIM keys, add the two CNAME records it shows in the Zone Editor, then switch on Sign messages for this domain with DKIM signatures (Microsoft's DKIM guide).

Microsoft recommends DMARC after SPF and DKIM, starting at p=none and moving to quarantine and then reject as the reports confirm your real mail passes (Microsoft's DMARC guide).

Mistakes that stop email working

Each of these is quick to avoid and slow to untangle once mail has gone missing.

  • Adding records in cPanel when Hosting.com does not answer the DNS. Check the nameservers first. Hosting.com says records added in cPanel with the nameservers elsewhere look correct and do nothing at all.
  • Leaving Email Routing on Local. With the MX pointed at Google or Microsoft, Local still tells the hosting server to keep the domain's mail. Set it to Remote Mail Exchanger.
  • Leaving cPanel's old MX record in place. cPanel's standard record sits at priority 0, the highest there is, so it can keep winning over the new one. Delete it when you add the new record.
  • A second SPF record. Two SPF records make SPF fail outright. Edit the one you have and keep every real sender in it.
  • Dropping the hosting include while the website still sends mail. A contact form that sends through the hosting server needs Hosting.com's include:spf.mysecurecloudhost.com in the SPF record, or that mail fails the check.
  • Switching MX before the new mailboxes exist. Incoming mail follows the MX record once the change spreads. Verify the domain, set up the accounts, then switch.
  • Adding Microsoft's autodiscover CNAME on top of cPanel's record. The name already has cPanel's autodiscover A record. Delete that first, or the CNAME cannot go in.
  • Starting DMARC at reject. Google, Microsoft and Hosting.com all start at p=none and tighten later, so real mail is not blocked by a setting nobody has watched yet.

Who this is for

  • Businesses whose website and domain are at A2 Hosting, now Hosting.com, setting up Google Workspace or Microsoft 365
  • Owners moving the business off the email that came with their cPanel hosting
  • Anyone whose Google or Microsoft setup is stuck at the verify your domain step
  • Owners who want to check the SPF, DKIM and DMARC records an earlier setup left behind

When this is not the right fit

  • Domains whose nameservers point somewhere other than Hosting.com. The records are the same, but they go on that company's DNS screen instead; for GoDaddy, see our GoDaddy DNS guide.
  • Moving existing mailboxes with years of mail in them. The records are the easy part of that job and the order is the hard part, covered in business email migration.

What TechTruePoint can help with

Adding the records takes minutes once you know where they go. Where owners ask for help is finding out who controls the DNS, the order of the switch, the cPanel settings that keep mail on the old server, and checking that mail really arrives afterwards.

Common questions

Is A2 Hosting the same company as Hosting.com?

Yes. A2 Hosting announced on April 28, 2025 that it is now Hosting.com. The old A2 website and customer login now open Hosting.com, and Hosting.com's knowledge base carries the help guides, including for domains bought from A2.

For DNS, little changed: a domain with an A2 hosting plan is still managed in cPanel's Zone Editor, as Hosting.com's DNS guide describes.

Do we have to move our domain or website away from A2 Hosting?

No. Google Workspace and Microsoft 365 both work with a domain and website that stay at A2 Hosting. All either one needs is a handful of records in cPanel and one change to Email Routing, which is what this guide covers.

The website keeps running from the hosting plan as before. Only the email moves.

What happens to the email already in our cPanel mailboxes?

It stays where it is. Once the MX record changes, new mail goes to Google or Microsoft, and Microsoft's guide says plainly that existing email stays at your previous email host unless you move it.

Copying years of old mail across is a separate job with its own order, covered in business email migration. Keep the cPanel mailboxes and the hosting plan until that copy is done and checked.

How long until Google or Microsoft sees the new record?

Usually not long. Hosting.com says MX and TXT changes usually take under an hour, though they can take several hours to show everywhere. Google says a new record can take up to 72 hours to be recognized.

Check rather than wait. When our free DNS lookup shows the new record, Google and Microsoft can see it too, and clicking Verify again is all that is left.

Get a Quote

Rather we added the records for you?

Tell us your domain and whether you are moving to Google Workspace or Microsoft 365. We check where your DNS is answered, add every record, set cPanel's Email Routing, and test sending and receiving before we hand it back.

Call now Request a quote