DS record
What is DS record?
A DS (Delegation Signer) record is a DNSSEC record a parent zone publishes holding a hash of a child zone's signing key, letting a resolver confirm the delegation is genuine. Defined in RFC 4034 and RFC 4035, it links a chain of trust from the DNS root down. AdminKit's DNS lookup tool shows a domain's DNSSEC chain, DS record included.
By AdminKit team, Netbase JSC · Updated
A DS (Delegation Signer) record is a DNSSEC record published in a parent zone that holds a cryptographic hash of a child zone’s DNSKEY, letting a validating resolver confirm the child’s signing key is the one the parent actually delegated to, without needing any prior trust relationship with the child zone itself. It is the link that turns a chain of individually signed zones into a single chain of trust running from the DNS root down to a specific domain, defined alongside the rest of DNSSEC in RFC 4034 and RFC 4035. The DS record’s Algorithm field uses the same signing-algorithm numbers tracked in IANA’s DNSSEC Algorithm Numbers registry. A domain adds DNSSEC by signing its own zone and then asking its registrar to publish a matching DS record at the parent; skipping that second step leaves the zone signed but unverifiable, since resolvers have no way to confirm the child’s key is genuine. ISC’s BIND DNSSEC Guide lists both steps: converting an insecure zone means creating DNSKEY, RRSIG and NSEC or NSEC3 records, then uploading verifiable information such as a DS record to the parent zone to complete the chain of trust.
AdminKit groups dS record under its DNS cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
What does a DS record actually contain?
A cryptographic hash of a child zone's DNSKEY, published in the parent zone, letting a validating resolver confirm the child's signing key is the one the parent actually delegated to.
Is signing a zone enough to turn on DNSSEC?
No -- a domain adds DNSSEC by signing its own zone and then asking its registrar to publish a matching DS record at the parent. Skipping that second step leaves the zone signed but unverifiable, since resolvers have no way to confirm the child's key is genuine.
Why does the DS record sit in the parent zone instead of the child's own zone?
Because it's what lets a resolver trust the delegation without any prior relationship with the child zone -- the parent is already trusted (via its own DS record or, at the root, via a built-in trust anchor), so its signed statement about the child's key extends that trust downward.
What RFCs define the DS record?
RFC 4034 defines the DNSSEC resource record formats, including DS, and RFC 4035 specifies the protocol modifications -- how a resolver actually uses those records to validate a chain of trust.