Google Cloud DNS signs a public zone with one setting and creates and rotates the keys itself — RSASHA256 by default. The DS record is added at the registrar; without it, signing does nothing.
| What it is | DNS host |
| DNSSEC | Yes |
| Signing | One setting per zone; keys created and rotated for you |
| Algorithm | RSASHA256 (8) by default; ECDSAP256SHA256 (13) available |
| DS record | No — add it at the registrar |
Is DNSSEC working for your domain?
Enter a domain: we read the DS record at its registry and the keys its nameservers publish, check that they match and the signatures are current, and ask a validating resolver.
Turning it on at Google Cloud DNS
- Cloud DNS, the zone, Edit, DNSSEC On, Save — or gcloud dns managed-zones update with –dnssec-state on.
- Copy the DS from the zone’s Registrar setup, and add it at the registrar.
Before moving the domain or its DNS
Turning it off: remove every DS at the registrar first, wait 24 hours or more, then switch DNSSEC off.
Moving to or from another signer: the Transfer state stops key rotation and imports the other operator’s keys, for a move with no gap. Do not leave a zone in it for more than a month or two.
Worth knowing
A zone with more than 3,000 record sets cannot have DNSSEC switched on or off: create a new, signed zone instead.
Cloud DNS denies names with NSEC3 by default — with one extra iteration and a salt, which RFC 9276 now advises against; NSEC can be chosen.
Avoid TTLs over three days in a signed zone: signatures expire at a fixed time.
Whose nameservers a domain uses: Google Cloud DNS’s.
Sources
Checked on 27 September 2026 against these official sources:
- DNS Security Extensions (DNSSEC) overview — docs.cloud.google.com
- Manage DNSSEC configuration — docs.cloud.google.com
- Use advanced DNSSEC — docs.cloud.google.com
- Activate DNSSEC — docs.cloud.google.com
- Migrate or transfer DNSSEC-enabled zones — docs.cloud.google.com
- RFC 9276: Guidance for NSEC3 Parameter Settings — rfc-editor.org