DNSSEC validation confirms that DNS responses are authentic and have not been altered between an authoritative source and a validating resolver. This guide provides a reusable workflow for checking DS and DNSKEY records, tracing the chain of trust, diagnosing validation failures, preparing for delegation changes, and completing a controlled DNSSEC key rollover.
Overview
DNSSEC adds cryptographic signatures to DNS data. A validating resolver begins with a configured trust anchor, normally the root, and follows a chain through the parent zone to the child zone. For a signed domain, the parent publishes a DS record that identifies a signing key in the child zone. The child publishes the corresponding DNSKEY record, along with signatures that allow resolvers to verify DNS answers.
A successful DNSSEC check therefore involves more than finding a DNSKEY record. The validator must confirm that the DS record in the parent matches an appropriate DNSKEY in the child, that the algorithm and digest are supported, that signatures are valid for the current time, and that negative answers are authenticated when a name or record does not exist.
When the chain is broken, validating resolvers may return a failure such as SERVFAIL rather than an ordinary “not found” result. Non-validating tools can still show apparently correct records, so troubleshooting should compare the authoritative data with the result from at least one DNSSEC-aware recursive resolver.
DNSSEC record comparison
| Record or concept | Where it appears | What to verify |
|---|---|---|
| DS | Parent zone | Key tag, signing algorithm, digest type, and digest match the intended child DNSKEY. |
| DNSKEY | Signed child zone | The expected key is published, has the correct flags and protocol fields, and uses the algorithm referenced by the DS. |
| RRSIG | Signed child zone | The signature covers the requested record set, uses the expected key, and is within its validity period. |
| NSEC or NSEC3 | Signed child zone | Negative answers are authenticated and the denial records are consistent with the zone. |
| CDS or CDNSKEY | Child zone, when used | Any automated delegation update reflects the intended rollover and is accepted by the registrar or parent operator. |
Checklist by scenario
Routine DNSSEC validation
- Confirm the exact domain and delegation you are testing. Check the apex separately from important subdomains.
- Query the parent zone for the DS record. Record the key tag, algorithm, digest type, and digest rather than relying on a simple “secure” status.
- Query the authoritative nameservers for DNSKEY records at the child zone apex.
- Calculate or inspect the DS derived from the candidate DNSKEY and compare every relevant field with the parent DS.
- Request a normal answer, such as an A, AAAA, MX, or TXT record, through a DNSSEC-validating recursive resolver.
- Check the validation status using a DNSSEC-aware command-line tool or DNSSEC checker. A positive answer alone does not prove that the chain validated.
- Test a deliberately nonexistent name beneath the zone. The response should provide authenticated denial when the zone is signed and the resolver supports DNSSEC validation.
After a registrar or nameserver change
- Export or record the current DS and DNSKEY data before changing delegation.
- Confirm that the new DNS provider has signing enabled and that its authoritative nameservers serve the intended DNSKEY, RRSIG, and denial-of-existence records.
- Check whether the provider generates a new key set. A nameserver migration that changes DNSKEY material requires a planned DS transition, not just a change to NS records.
- Verify that the registrar has published the intended DS at the parent. Do not assume a control-panel status represents what is publicly delegated.
- Query both old and new authoritative servers during the transition. Inconsistent answers can create intermittent validation failures.
- Keep the previous signing configuration available until the delegation and resolver observations are stable according to your change plan.
DNSSEC key rollover
Separate the role of the key that signs zone data from the key used to establish the delegation when your DNS platform supports that distinction. The exact procedure depends on the provider, registrar, and rollover method, but the safety principle is consistent: avoid a period in which the parent points only to a key that the child has not published, and avoid removing a key while valid signatures or cached DS data may still depend on it.
- Identify the current key material, DS record, rollover type, and planned maintenance window.
- Confirm algorithm and digest compatibility with the registrar and DNS provider. Platform interfaces may label these options differently.
- Publish the new DNSKEY while retaining the old key as required by the rollover procedure.
- Wait for the relevant publication and caching intervals defined by your operational plan.
- Publish or replace the parent DS so that it references the new key. If using CDS or CDNSKEY automation, verify that the parent actually consumes the proposed update.
- Validate through independent recursive resolvers and query the authoritative servers directly.
- Remove the old DS and DNSKEY only after the new chain validates and the old data is no longer needed for the planned transition.
When validation fails
- Capture the exact query name, record type, resolver, timestamp, and response code. DNSSEC failures can vary by name and resolver.
- Start at the parent DS and compare it with the child DNSKEY. A stale, mistyped, or incorrectly derived digest is a common break in the chain.
- Check RRSIG expiration, inception times, signer names, key tags, and algorithms. Also verify that authoritative servers have synchronized time and zone data.
- Test each authoritative nameserver independently. One server serving a different key set can produce inconsistent results.
- Check delegation records, including NS and glue where applicable. A DNSSEC repair cannot compensate for an incorrect delegation.
- After correcting the configuration, repeat both positive-answer and authenticated-denial tests. Record the evidence for the change review.
What to double-check
Parent and child agreement: The DS record belongs to the parent, while the DNSKEY belongs to the child. Checking only the child zone can miss a broken delegation. Compare the key tag, algorithm, digest type, and digest as a complete set.
Algorithm and digest handling: Do not substitute an algorithm number or digest type from a different key. Confirm that the registrar, DNS provider, and resolver tools support the configuration you intend to deploy. Supported options and user-interface labels can change, so review current provider documentation before a rollover.
Signature time: RRSIG records have inception and expiration values. Clock errors, delayed publication, or an unexpectedly short signing window can make otherwise correct data fail validation.
Authenticated denial: A signed zone must be able to prove that a requested name or record is absent. Inspect NSEC or NSEC3 responses when testing nonexistent names; a positive lookup does not test this part of DNSSEC.
Delegation boundaries: A signed parent does not automatically mean every child is signed. For a delegated subdomain, verify its own DS relationship and signing state. Conversely, an intentionally unsigned child should be represented consistently rather than leaving stale DS data at the parent.
Resolver perspective: Authoritative queries show what the zone serves; recursive queries show what a validating client can use. Use both perspectives and retain command output or checker results with the change record.
Common mistakes
- Changing nameservers and DS records in one unplanned step. Treat delegation and signing material as related but separate changes, with a rollback path for each.
- Deleting the old key too early. During a rollover, retained keys may still be needed to validate signatures or cached delegation data.
- Trusting a single online checker. A checker can be useful, but verify its result against authoritative queries and an independent validating resolver.
- Confusing DNSSEC with encryption. DNSSEC provides authenticity and integrity signals for DNS data; it does not encrypt ordinary DNS queries or application traffic.
- Ignoring time and cache behavior. Publication, signature validity, and recursive caching all affect what different observers see during a change.
- Testing only the apex. Mail records, service subdomains, and delegated zones can have different signing and delegation paths.
- Removing a DS without understanding the intended state. If a zone is meant to remain signed, removal can weaken the configuration; if it is being intentionally unsigned, stale DS data can cause validation failures.
When to revisit
Use this checklist before a domain launch, registrar migration, nameserver replacement, DNS provider change, signing-key rotation, or major zone redesign. It is also useful during recurring DNS security audits and before seasonal planning cycles when infrastructure ownership or deployment workflows may change.
Revisit the guide whenever your registrar or DNS provider changes its DNSSEC controls, automated DS workflow, supported algorithms, or rollover procedure. Resolver behavior and operational tooling can also evolve, so refresh the commands and checker steps used by your team rather than copying an old runbook indefinitely.
For a practical change record, save the pre-change DS and DNSKEY values, authoritative responses from each nameserver, validating-resolver results, the planned waiting intervals, and post-change evidence. If DNSSEC is part of a broader secure deployment review, pair this workflow with the Domain and SSL Certificate Validation Checklist. For related DNS authentication troubleshooting, see the SPF, DKIM, and DMARC Validation Guide.
Before approving the change: confirm the parent DS matches the intended child DNSKEY, every authoritative server agrees, positive and negative queries validate, and the rollback steps are documented. That final evidence turns DNSSEC validation from a one-time check into a repeatable operational control.