Moving domain to Google Workspace, correct record bundle unclear
Google Workspace as of 2023 uses a single MX (smtp.google.com priority 1) instead of the old five records. SPF and DKIM remain, MX and SPF are the must-haves for delivery.
Try this first
- 1MX: a single record, smtp.google.com priority 1. The old ASPMX/ALT* set can be removed after migration.
- 2SPF (TXT at apex): v=spf1 include:_spf.google.com ~all. Do not stack multiple SPF records, use includes.
- 3DKIM: in Workspace admin under Apps > Gmail > Authenticate email, generate a 2048-bit key. Place the TXT at google._domainkey.yourdomain. Only click 'Start authentication' after the TXT is live.
- 4Domain verification: a temporary TXT 'google-site-verification=...' at apex to prove ownership, can be removed after verification.
- 5Teams equivalent: Google Meet needs no extra SRVs. Calendar works with SPF and DKIM alone.
When to bring us in
If you migrate during business hours and want dual delivery during cutover, we can plan it with a test account and monitoring.
See also
- Domain expires tomorrow and nobody saw the emailAn expired domain doesn't transfer instantly. There's a redemption window, but you pay extra.
- Unsure whether to enable auto-renewDisabling auto-renew only makes sense for domains you'll truly drop. For anything live, just keep it on.
- New registrar asks for auth code, can't find itEPP code or transfer code is the password to move a domain from registrar A to B.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.