CDS/CDNSKEY record
What is CDS/CDNSKEY record?
A CDS or CDNSKEY record, defined in RFC 7344, lets a DNSSEC-signed domain automate updating the DS record its parent zone publishes, instead of a human copying a key fingerprint into a registrar panel by hand. AdminKit's DNSSEC guide covers the stale-DS-record failure this automation exists to prevent.
By AdminKit team, Netbase JSC · Updated
CDS and CDNSKEY records, defined in RFC 7344 (document record at the IETF Datatracker), let a DNSSEC-signed domain automate updating the DS record its parent zone publishes, instead of relying on a human to copy a new key fingerprint into a registrar’s control panel by hand. A domain’s own DNS operator — the “child” side of the delegation — publishes a CDS (Child DS) or CDNSKEY (Child DNSKEY) record in its own zone, stating exactly what it wants the parent zone’s DS record to contain — CDS and CDNSKEY are registered as RR types 59 and 60 in IANA’s DNS Parameters registry. A registry or registrar that supports RFC 7344, acting as the “parental agent,” periodically polls the child zone for these records and, once it finds a validly signed CDS or CDNSKEY, updates the actual DS record at the parent automatically, with no manual registrar-panel step required. On the child side, PowerDNS’s DNSSEC operational instructions enable CDS/CDNSKEY publication with pdnsutil zone set-publish-cds or pdnsutil zone set-publish-cdnskey, and note that because initial bootstrapping has no pre-existing chain of trust, some registries observe these records for a few days before acting on them. Knot DNS’s configuration guide describes the same pattern in an automated KSK rollover: the server publishes CDS and CDNSKEY records, then periodically checks the parent zone for the matching DS before finishing the rollover. RFC 8078 later elevated this mechanism to Standards Track and added a “delete algorithm” so a child can also signal the parent to remove DNSSEC entirely. This closes one of DNSSEC’s most common operational failure modes: a key rollover where the domain’s own DNSKEY changes but the parent zone’s DS record is never updated to match, breaking validation for every resolver checking that chain until someone notices and fixes the mismatch by hand.
What CDS/CDNSKEY automation replaces:
- Manual step: copying a new DS key fingerprint into a registrar control panel by hand.
- Automated step: the registrar polls the child zone and updates the parent’s DS record itself.
- RFC 8078 extension: a child zone can also signal the parent to remove DNSSEC delegation entirely.
CDS/CDNSKEY record is part of AdminKit’s DNS cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What manual step do CDS/CDNSKEY records remove?
Copying a new DS key fingerprint into a registrar's control panel by hand -- a registrar that supports RFC 7344 polls the child zone and updates the parent's DS record automatically instead.
Who publishes a CDS or CDNSKEY record?
The domain's own DNS operator, the 'child' side of the delegation, publishes it in its own zone to state what it wants the parent zone's DS record to contain.
What did RFC 8078 add to this mechanism?
Standards Track status and a 'delete algorithm,' letting a child zone also signal the parent to remove DNSSEC delegation entirely.
What DNSSEC failure does this automation prevent?
A key rollover where the domain's own DNSKEY changes but the parent zone's DS record is never updated to match, breaking validation until someone notices and fixes the mismatch by hand.
Sources
- RFC 7344 -- Automating DNSSEC Delegation Trust Maintenance
- RFC 8078 -- Managing DS Records from the Parent via CDS/CDNSKEY
- IANA -- Domain Name System (DNS) Parameters registry (Resource Record TYPEs)
- IETF Datatracker -- RFC 7344 document record
- PowerDNS Authoritative Server documentation -- Operational instructions (DNSSEC)
- Knot DNS documentation -- Configuration