DNS provider
Add an SPF record in Google Cloud DNS
SPF must be a single TXT starting with v=spf1 at the domain that sends mail. Google Cloud DNS will let you break this with duplicate TXT — don’t.
Provider gotcha: The DNS name field for apex records must use a trailing dot:
example.com. — FQDN form. Omitting the dot can create the wrong relative name.Reference: SPF DNS.
Step by step
Step 1 Google Cloud Console → Network services → Cloud DNS → your zone → Add standard (or Add record set).
Step 2 TXT record. For root domain SPF: Use FQDN with trailing dot for clarity on apex; for
_dmarc use _dmarc.example.com. in the name field..Step 3 Single SPF only — merge vendors into one string:
v=spf1 include:_spf.google.com ~all
Step 4 Save. The DNS name field for apex records must use a trailing dot:
example.com. — FQDN form. Omitting the dot can create the wrong relative name.Step 5 Propagation: Usually minutes once the zone is live at Google’s nameservers.
Step 6 Use DNS Preflight — SPF tree shows lookup count. Link: SPF guide.
DNS Preflight — full auth check for your domain.
Propagation — compare resolvers.
FAQ
Can I add two SPF TXT records?
No — merge into one v=spf1 string or you get PermError.
How does Google Cloud DNS want SPF quoted?
Follow the code block on this page; Route 53 requires quotes around the full TXT.
Why PermError after saving?
Syntax error, duplicate SPF, or over 10 DNS lookups — use Preflight’s SPF tree.
Include SendGrid and Google?
Yes in one record: v=spf1 include:... include:... ~all — watch lookup count.
How long until live?
Usually <strong>minutes</strong> once the zone is live at Google’s nameservers.