Once a zone is active on Cloudflare, how do you turn on DNSSEC, and what must happen at the registrar before it takes effect?
answer
- Cloudflare signs, the parent vouches
- Enable DNSSEC on DNS Settings
- Algorithm 13 DS at the registrar
- pending until the DS appears
- remove the DS before turning off
basics
~20 sSelect Enable DNSSEC on the zone's DNS Settings page: Cloudflare signs the zone and shows a DS record, which you add at the registrar. DNSSEC stays pending until the DS is published; Cloudflare Registrar domains get theirs automatically.
solid answer
~50 sOn the zone's **DNS Settings** page, select **Enable DNSSEC**. Cloudflare signs the zone, publishes its public keys and generates a **DS record**, whose values the dialog shows and the **DNSSEC** card keeps. You add that DS at the registrar; Cloudflare uses **Algorithm 13** (ECDSA Curve P-256 with SHA-256), so pick that if the registrar asks. Until the DS is published Cloudflare reports `pending` and already signs the zone; once the parent serves the DS it reports `active`. Domains on **Cloudflare Registrar**, and `.ch` and `.cz` domains, get the DS added automatically from Cloudflare's CDS and CDNSKEY records, which can take one to two days on Registrar. To turn it off, remove the DS at the registrar; Cloudflare keeps signing after you disable DNSSEC, and the records should be deleted, which stops signing, only once at least 1.5 times the DS TTL has passed.
go deeper
Recall the two halves: Cloudflare signs after Enable DNSSEC, and the DS record must be added at the registrar before validation works.
Explain the pending, active, pending-disabled and disabled states, what Cloudflare serves in each, and why the DS uses Algorithm 13.
Show the safe order for turning DNSSEC off and why deleting the records is the risky step, how CDS and CDNSKEY drive automatic DS changes, and how to verify with the ad flag and RRSIG records.
Treat DNSSEC as a two-party control: who owns registrar access, who may remove a DS, and how a migration or provider change is sequenced.
## What enabling DNSSEC does on Cloudflare DNSSEC adds signatures to DNS answers so that a **validating resolver** can prove they came from the zone's owner unchanged. Two parties must take part. The **DNS provider** signs the zone and publishes its public keys (`DNSKEY` records), and the **parent zone**, through the registrar, publishes a **DS record** that vouches for the zone's key-signing key. Signing without the DS gives validators nothing to anchor to; a DS without matching signatures makes the zone fail validation. When you select **Enable DNSSEC**, Cloudflare does its half: it signs the zone, publishes the keys and generates the DS. The other half is yours. ## Turning it on 1. **Make sure the zone is active** on a full setup, with Cloudflare authoritative. 2. **Enable it in Cloudflare.** Go to **DNS Settings** and select **Enable DNSSEC**. The dialog shows the DS values; after you close it, **DS record** on the **DNSSEC** card shows them again. 3. **Add the DS at the registrar.** Cloudflare's preferred algorithm is **Algorithm 13**, which some registrars label **ECDSA Curve P-256 with SHA-256**. 4. **Wait for the parent to publish it**, then confirm. ## The DNSSEC states | State | Meaning | | --- | --- | | `pending` | Enabled in Cloudflare; the DS is not yet at the registrar | | `active` | Enabled, and Cloudflare's DS is present at the registrar | | `pending-disabled` | Disabled in Cloudflare, but the DS is still at the registrar | | `disabled` | Disabled, and the DS has been removed | In `pending` and `active`, Cloudflare signs the zone and serves `RRSIG`, `NSEC`, `DNSKEY`, `CDS` and `CDNSKEY` records. In `pending-disabled` and `disabled` it still signs and serves `RRSIG`, `NSEC` and `DNSKEY`, but sets `CDS` and `CDNSKEY` to the zero (delete) form, telling the registrar to drop the DS. The DNSSEC records can be deleted through the API only from `disabled`; Cloudflare refuses while `active`, so a DS cannot be left pointing at keys that no longer exist. ## Verifying - `dig example.com +dnssec` shows the `RRSIG` lines beside the answer. - `dig DNSKEY example.com +short` lists the keys: flag `257` is the key-signing key, `256` the zone-signing key. - A plain `dig example.com` through a validating resolver shows the `ad` flag when the answer validated. - On Cloudflare Registrar, the dashboard shows a confirmed status, and WHOIS reads `signedDelegation`. ## Turning it off without an outage 1. **Remove the DS at the registrar**, or select **Disable DNSSEC** on Cloudflare Registrar. Disabling DNSSEC in Cloudflare is safe at any point here: in `pending-disabled` and `disabled` the zone stays signed and the zero-form `CDS` and `CDNSKEY` ask the registrar to drop the DS. 2. **Keep the zone signed** until the DS has expired from caches at the parent's TTL; resolvers holding a cached DS still expect signatures. Cloudflare's rule of thumb is to wait at least **1.5 times** the DS TTL, so 36 hours for a 24-hour DS. 3. **Optionally delete the DNSSEC records** with the Delete DNSSEC API call, moving the zone to the `deleted` state: signing stops and `RRSIG`, `NSEC`, `DNSKEY`, `CDS` and `CDNSKEY` disappear. The step that causes an outage is the last one done too early: once signatures and keys are gone while a resolver still trusts a cached DS, that resolver rejects the zone. A `disabled` zone still serving `DNSKEY` records is expected behaviour, although some audit tools report it as a `DNSKEY` with no DS; deleting the records after the wait is what clears it. ## Special cases - **Cloudflare Registrar.** DNSSEC is one click under **Configuration** > **Enable DNSSEC**. Cloudflare publishes `CDS` and `CDNSKEY` records, the Registrar scans them and sends the DS to the registry, which can take one to two days. - **`.ch` and `.cz` domains** also get the DS added automatically. - **A registrar without Algorithm 13.** Ask it to support modern algorithms, or move the domain to a registrar that does. - **More than one DNS provider.** A primary zone with multi-provider DNS needs **multi-signer DNSSEC**, and secondary and subdomain zones have their own DNSSEC options.
- Why does Cloudflare keep signing a zone in the pending-disabled state?In `pending-disabled` the DS is still at the registrar, so validating resolvers still expect signatures. If Cloudflare stopped signing, every validator that trusts the DS would reject the zone. It keeps signing and sets `CDS` and `CDNSKEY` to the delete form, signalling the registrar to remove the DS, until the DS is gone and the state reaches `disabled`.
- The registrar's DNSSEC form offers only RSA algorithms. What are your options for a zone on Cloudflare?Cloudflare signs with Algorithm 13, ECDSA Curve P-256 with SHA-256, and its DS must say so. Ask the registrar to add support for Algorithm 13, or transfer the domain to one that has it, Cloudflare Registrar included. If the top-level domain itself lacks Algorithm 13, the registry has to add it.
- Clicking Enable DNSSEC in Cloudflare is all it takes for validation to work.
- Cloudflare starts signing only after it sees the DS at the registrar.
- Disabling DNSSEC in Cloudflare stops it signing the zone straight away.
- Any DS algorithm the registrar offers will match Cloudflare's keys.
- Every domain on a paid Cloudflare plan gets its DS published automatically.