Guide per DNS host

Enable DNSSEC at Cloudflare

Cloudflare signs any zone with one click on request. DNSSEC is only complete, however, once the DS record is published at the domain’s registrar, and that second step is the one most often forgotten. This guide shows both steps and the order when migrating.

Cloudflare: all records at a glance

DNSSEC at Cloudflare: the status

You switch on DNSSEC in the Cloudflare dashboard in the domain’s DNS settings. Cloudflare signs the zone with algorithm 13 (ECDSA P-256 with SHA-256) and then shows the DS record values: key tag, algorithm, digest type and digest.

These values belong at the domain’s registrar, the place where the domain is registered. Only once the DS record is at the registry is the chain complete. This is automatic for domains registered through Cloudflare Registrar and, according to Cloudflare, for .ch and .cz domains; at Cloudflare Registrar publication can take one to two days.

When moving an already signed domain to Cloudflare the order matters: first disable DNSSEC at the current registrar and wait until the old DS record has expired, then change the name servers, and finally enable DNSSEC at Cloudflare and publish the new DS record. Changing name servers with the old DS record still active yields SERVFAIL instead of answers.

How to enable DNSSEC at Cloudflare

The way through the Cloudflare control panel:

  • In the Cloudflare dashboard open the domain and go to “Settings” under “DNS”.
  • On the “DNSSEC” card choose “Enable DNSSEC”; Cloudflare shows the DS record values.
  • Create a DS record with exactly these values at the domain’s registrar. Many registrars have a dedicated DNSSEC section, at some support enters the data.
  • Wait until Cloudflare shows DNSSEC as active and verify the chain with the checker. The values can be shown again later via “DS record” on the same card.

Click path at Cloudflare

Official guide from Cloudflare: DNSSEC(opens in a new tab)retrieved 10 Nov 2026

The order when changing providers

DNSSEC does not forgive a wrong order. The DS record at the registry points to the key of the zone; if the two do not match, validating resolvers answer with SERVFAIL and the domain is unreachable for many users, website and mail included.

  • Before changing name servers switch off DNSSEC or remove the DS record.
  • Wait until the TTL of the DS record has expired, usually one to two days.
  • Only then change the name servers and sign again at the new provider.

Verify and keep an eye on it

The DNSSEC checker below follows the chain from the registry to the zone: DS record, DNSKEY and signatures. You see right away whether DNSSEC is fully set up for a domain at Cloudflare or whether an orphaned DS record puts the domain at risk. DomainWarn keeps checking this afterwards and alerts you when the chain breaks or signatures expire.

Frequently asked questions

DNSSEC is enabled at Cloudflare but the checker finds no DS record. Why?
Because the DS record is missing at the registrar. Cloudflare signs the zone but can only set the record at the registry itself for domains at Cloudflare Registrar and a few extensions. Publish the values from the dashboard at the registrar.
How do I switch DNSSEC off again at Cloudflare?
Remove the DS record at the registrar first and wait until its TTL has expired, and only then disable signing at Cloudflare. In the opposite order the domain is unreachable for validating resolvers.
How do I know whether DNSSEC is active for my domain?
By the DS record at the registry and the signatures in the zone. The DNSSEC checker shows both and names the point where the chain breaks.
Check now

Free DNSSEC test: DS record, resolver validation and broken signature chains. Shows whether validating resolvers like Google and Cloudflare still reach you.

DomainWarn checks SPF, DKIM, DMARC, DNS and certificates of all client domains regularly and reports changes before mail lands in spam.

Monitor this domain continuously14-day free trial, no credit card.

The same guide for other hosts

All hosts at a glance