Email provider
Google Workspace DNS records
Gmail for your own domain, managed from the Google Admin console.
Where is your domain's DNS managed?
Each guide below uses that host's field names, steps and known problems.
- Amazon Route 53 Google Workspace on Amazon Route 53
- Bluehost Google Workspace on Bluehost
- Cloudflare Google Workspace on Cloudflare
- DreamHost Google Workspace on DreamHost
- GoDaddy Google Workspace on GoDaddy
- Hostinger Google Workspace on Hostinger
- IONOS Google Workspace on IONOS
- Name.com Google Workspace on Name.com
- Namecheap Google Workspace on Namecheap
- Network Solutions Google Workspace on Network Solutions
- OVHcloud Google Workspace on OVHcloud
- Porkbun Google Workspace on Porkbun
- SiteGround Google Workspace on SiteGround
- Squarespace Domains Google Workspace on Squarespace Domains
- Wix Google Workspace on Wix
- WordPress.com Google Workspace on WordPress.com
The records Google Workspace needs
These are the values for any DNS host. Field names differ between hosts, so use the host guides above for the exact boxes to fill in.
| Record | Type | Host / Name | Value | Priority | TTL | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Domain verification Proves you own the domain | Type | TXT | Host / Name | @ | Value | Copy from Google Admin console Looks like: google-site-verification= followed by your unique code | Priority | n/a | TTL | Default |
| MX records Where incoming email goes | Type | MX | Host / Name | @ | Value | smtp.google.com | Priority | 1 | TTL | Default |
| SPF record Which servers may send as you | Type | TXT | Host / Name | @ | Value | v=spf1 include:_spf.google.com ~all | Priority | n/a | TTL | Default |
| DKIM A signature on every message | Type | TXT | Host / Name | google._domainkey | Value | Copy from Google Admin console | Priority | n/a | TTL | Default |
| DMARC record What to do with fakes · recommended | Type | TXT | Host / Name | _dmarc | Value | v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com | Priority | n/a | TTL | Default |
Common Google Workspace mistakes
Leaving old MX records in place
Google says email might not work correctly if old or incorrect MX records stay. Remove every MX record except smtp.google.com.
Adding a second SPF record
A domain must have only one SPF record. If you already have one, add include:_spf.google.com to it instead of creating another.
Generating the DKIM key too soon
Google asks you to wait 24 to 72 hours after turning on Gmail before generating the DKIM key.
Publishing DKIM but not turning it on
Adding the TXT record is only half the job. Go back to Authenticate email in the Admin console and turn on authentication.
Deleting the verification record too early
Removing the google-site-verification record before Google confirms the domain makes verification fail.
Check your Google Workspace DNS
Enter your domain to see which records are in place.
Sources
- Recommended DMARC rollout (Google Workspace Help) Checked October 21, 2026
- RFC 7208: Sender Policy Framework (IETF) Checked October 21, 2026
- Set up DKIM (Google Workspace Help) Checked October 21, 2026
- Set up DMARC (Google Workspace Help) Checked October 21, 2026
- Set up MX records for Google Workspace (Google Workspace Help) Checked October 21, 2026
- Set up SPF (Google Workspace Help) Checked October 21, 2026
- Verify your domain with a TXT record (Google Workspace Help) Checked October 21, 2026
Rather have someone do it for you?
Tell us your domain and we will add and verify every record for your email, then send you the check results.