Skip to content
nofeb

SPF, DKIM, DMARC and MX on Google Cloud DNS

DNS host detected from nameservers under *.googledomains.com

On Google Cloud DNS, add the records by hand in Google Cloud DNS's DNS form: labels such as bounce, apex as an empty name, TXT in double quotes, targets ending in a dot. nofeb detects Google Cloud DNS and returns each record in that shape.

Checked against the engine on .

How does nofeb know the domain is on Google Cloud DNS?

It looks up the zone's NS records and matches the nameserver hostnames. Nameservers under *.googledomains.com mean Google Cloud DNS. When a zone is split between two hosts during a move, the host serving most of its nameservers wins.

How do I add the records on Google Cloud DNS?

Open Google Cloud DNS's DNS page for the domain (Google Cloud DNS DNS console) and add each record from the table below. Then ask nofeb to check: POST /v1/domains/{domain_id}/verify.

What exactly do I type in Google Cloud DNS's record form?

Shown for example.com as Google Cloud DNS wants it; placeholder values come from your dns-setup response.

RecordTypeName boxValue boxPriority
DKIM key 1 CNAME token1._domainkey target-1-from-nofeb. —
DKIM key 2 CNAME token2._domainkey target-2-from-nofeb. —
DKIM key 3 CNAME token3._domainkey target-3-from-nofeb. —
MAIL FROM MX MX bounce feedback-host-from-nofeb. 10
MAIL FROM SPF TXT bounce "v=spf1 include:<value from nofeb> ~all" —
DMARC TXT _dmarc "v=DMARC1; p=none; rua=mailto:dmarc@example.com" —
Inbound MX (optional) MX (leave empty) inbound-host-from-nofeb. 10

Which form rules does Google Cloud DNS follow?

  • Google Cloud DNS appends .example.com to whatever you type in the name box, so type only the label, for example bounce. Typing the full name creates bounce.example.com.example.com.
  • For the domain itself (the apex), leave the name box empty.
  • TXT values go in double quotes: paste them with the quotes. Values over 255 characters are split into several quoted strings.
  • CNAME and MX targets need a trailing dot, or Google Cloud DNS appends your domain to the target.
  • MX priority has its own field: use 10.

What goes wrong most often on Google Cloud DNS?

  1. The domain appended twice (bounce.example.com.example.com) from typing the full name. The live check names this mistake when it sees it.
  2. A TXT value pasted without quotes, or a long value not split into 255-character strings.
  3. A CNAME target without its trailing dot, which Google Cloud DNS turns into target.example.com.
Publishing email DNS records on Google Cloud DNS Add a domain; nofeb detects the DNS host from its NS records. Then one of three paths: a one-click Domain Connect link (Beta), publishing through the host's API with a token used once (Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun, Gandi), or instructions written for that host plus zone-file, Route 53 and Terraform exports. Every record is then checked live, showing what was found and the likely mistake, and domain.verified is emitted when all pass. Add the domain POST /v1/domains records generated Detect the DNS host from its nameservers GET …/dns-setup One-click Domain Connect sign in at the host, click Connect Beta Published through the API token used for one call, never stored POST …/dns/apply Instructions for that host host and value boxes, as its form wants zone file · Route 53 · Terraform Live check found value and likely fix domain.verified
nofeb looks up who runs Google Cloud DNS from its nameservers, takes the shortest path that host allows, then checks every record live until domain.verified fires.

Frequently asked questions

Do I type the full domain in Google Cloud DNS's name field?

No. Google Cloud DNS appends .example.com itself, so for the MAIL FROM records type bounce. Typing the full name creates bounce.example.com.example.com, and nofeb's live check reports exactly that.

Does Google Cloud DNS need quotes around TXT values like DMARC?

Yes. Paste "v=DMARC1; p=none; rua=mailto:dmarc@example.com" including the quotes; Google Cloud DNS stores the value as typed.

Where are the DNS records in Google Cloud DNS?

In Google Cloud DNS's DNS page: console.cloud.google.com/net-services/dns/zones. The dns-setup response links the same page for your domain.

Can nofeb add the records on Google Cloud DNS automatically?

Not by API token. Google Cloud DNS gets the records shaped for its form.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
Custom domains Add a domain and nofeb returns its DKIM, custom MAIL FROM and DMARC records, plus an inbound MX if you want nofeb to receive its mail, checks them, and emits domain.verified when they pass. Shipped
DNS setup made easy nofeb detects who hosts your domain's DNS and gives you the shortest path for that host. It can publish the records through the Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi API with a token used for that one call and never stored, and it never deletes a record. Every other host gets step-by-step instructions in its own terms, plus zone-file, Route 53 and Terraform exports. A live check shows each record's status, what was found and the likely mistake. Pointing your MX at nofeb is a separate choice, so publishing sending records never moves your mail. Shipped
Inbound mail server that checks mail at the door nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. Shipped