Topic · DNS & Infrastructure
DNSSEC DS record
A DS record connects a child zone's DNSSEC signing key to its parent zone's authenticated delegation.
How it works
Validating resolvers use the parent's DS digest to establish a chain of trust into the signed child zone.
What can go wrong
A stale DS after key rotation or provider migration can cause DNSSEC validation failure and SERVFAIL.
What to check or do
Coordinate DS changes with DNSKEY publication and test validation externally before retiring keys.
Practical scenario
An organization migrates to a managed DNS service and rotates DNSSEC keys. The registrar still publishes a DS digest for the old signing chain, so validating resolvers reject the new zone as bogus.
Verification checklist
- Check the parent DS and active child DNSKEY set.
- Verify digest algorithms and keys match the intended rollover state.
- Confirm authoritative signatures and expiration periods.
- Sequence registrar and DNS provider updates with a tested overlap plan.
How to investigate DNSSEC DS record
- Signal to investigate
- The registry still serves a DS digest for keys no longer available at the child zone.
- Evidence to collect
- Compare parent DS digests against the active child DNSKEY and planned rollover.
- Common wrong conclusion
- A DS mismatch can make an otherwise healthy DNS zone invisible to validating clients.
dig +dnssec DS example.comEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.