Topic · DNS & Infrastructure
DNSSEC
Domain Name System Security Extensions provide cryptographic integrity for signed DNS answers.
How it works
Resolvers validate signatures through DNSKEY, DS and chained trust information.
What can go wrong
A broken DS or expired signature can make an otherwise healthy domain unreachable.
What to check or do
Coordinate registrar and DNS-operator changes and monitor validation failures.
Practical scenario
A company migrates its DNS hosting but leaves a DS record at the registry pointing to the old key. Nonvalidating resolvers may still answer correctly, while validating resolvers return SERVFAIL for the signed zone.
Verification checklist
- Inspect DS records at the parent zone and DNSKEY records at the child.
- Verify RRSIG status from independent validating resolvers.
- Sequence key rotations and DNS provider changes deliberately.
- Do not treat a visible record in one resolver as proof of DNSSEC health.
How to investigate DNSSEC
- Signal to investigate
- A delegation change causes SERVFAIL only at validating resolvers.
- Evidence to collect
- Check parent DS, child DNSKEY and signed RRsets as one trust chain.
- Common wrong conclusion
- Turning off DNSSEC in a DNS dashboard without updating parent DS can break resolution.
How to interpret the evidence
DNSSEC adds authenticated data origin and integrity to DNS answers by validating a chain from parent DS records to child DNSKEYs and signed data. A broken chain can return SERVFAIL for validating clients even though an authoritative server is answering the underlying TXT or MX query correctly. This often surfaces during DNS-provider migrations or badly sequenced key rotations.
What to change and how to verify it
Compare parent DS against current child keys, signatures and their validity periods. Test through a validating resolver and repair the parent-child chain using the DNS operator's rollover procedure. Avoid toggling signing off without ensuring the parent delegation is updated as required.
delv example.com TXTEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.