Google Workspace: what you should know
Google Workspace gets by with few records: one MX record to smtp.google.com, the SPF record with include:_spf.google.com and a TXT record for DKIM at google._domainkey. You generate the DKIM key yourself in the Admin console; without that step and the click on “Start authentication” Gmail does not sign with your domain.
Google is also the strictest receiver: anyone sending to Gmail accounts needs SPF or DKIM, and anyone sending around 5,000 messages or more a day there must have SPF, DKIM and a DMARC record. Setting up your own Workspace domain properly is therefore also the precondition for newsletters reaching Gmail recipients.
The domain must be verified in the Admin console; after turning on Gmail it takes 24 to 72 hours before a DKIM key can be generated.
The values for Google Workspace at a glance
The records Google Workspace expects for a custom domain; the guides above cover the details.
- MX: 1 smtp.google.com
- SPF: v=spf1 include:_spf.google.com ~all
- DKIM: With Google Workspace you generate the DKIM key yourself in the Admin console and publish the public part as a TXT record. The default selector is google, so the record lives at google._domainkey. Google offers 2048 bits; 1024 bits is only meant for DNS hosts that cannot store values that long.
- DMARC: Google describes DMARC as the third step after SPF and DKIM and recommends waiting 48 hours after setting those up. The record is a TXT record at _dmarc at the DNS host; the Admin console has no setting for it. You start with p=none and a rua address, then move step by step through quarantine to reject.
Where to create the records
Google Workspace specifies the values; they are created at the domain’s DNS host, the place the name servers point to. The guides by host show the way to the DNS editor of IONOS, STRATO, Hetzner, Cloudflare and other providers.