DNSSEC: DNS Signatures, DS and Validation
DNSSEC adds origin authentication and data integrity to DNS data through digital signatures and a chain of trust. It does not encrypt the query name or the DNS transport.
Updated · Editorial approach and simulation limits
DNSKEY and RRSIG bind signed DNS data
A signed zone publishes DNSKEY records and RRSIG records. The DNSKEY identifies a public key used to verify signatures over DNS data. An RRSIG covers a resource-record set and includes a validity interval; a validator checks the signature and whether the answer falls within that interval.
A DS record in the parent zone links to a key in the child zone. Following these links from a trust anchor lets a validating resolver establish a chain of trust. If any required link or signature fails validation, the resolver can return a DNSSEC validation error rather than treating the data as securely authenticated.
Validation can be performed at different points
A recursive resolver may validate DNSSEC on behalf of its clients, or a client may validate data itself. A trace at the client can show the AD flag or DNSSEC-related records, but the flag’s meaning depends on trust in the resolver and on the client’s configuration.
A signed response is not automatically proof that every client validated it. Check whether the resolver is configured to validate, whether the response includes the relevant records, and whether the client trusts the resolver’s assertion. DNSSEC authenticates DNS data within its chain; it does not certify that a website is safe or that a server’s application content is benign.
DNSSEC is not encrypted DNS
DNSSEC signatures help detect forged or modified data in transit or at a resolver. They do not hide the queried name. DNS over HTTPS and DNS over TLS encrypt the path between a client and its chosen resolver, but they do not themselves prove that a returned DNS answer is authentic.
A DNSSEC-enabled lookup can travel over ordinary DNS, DoT or DoH. These protections can coexist: DNSSEC checks data authenticity, while encrypted DNS protects the transport path to the selected resolver. The operator of that resolver can still see the query.
Diagnose validation failures from the chain
When a lookup returns SERVFAIL on a validating resolver, compare it with a non-validating diagnostic query only in a controlled troubleshooting context, then inspect the DNSSEC chain for missing DS or DNSKEY records, expired signatures, algorithm mismatch or incorrect authoritative data. The point is to locate the broken link, not to disable validation as a permanent fix.
Protocol Explorer shows a simplified signed-answer path. It does not validate live DNS records. Use the DNSSEC RFCs and a trusted diagnostic tool against the domain in question, and keep the resolver and validation settings explicit in your report.
Follow the chain from a trust anchor to the answer
A validating resolver does not trust a DNSKEY merely because it appears in a response. It starts with a configured trust anchor, normally the root zone’s key material, and verifies signatures down the delegation chain. A parent zone publishes a DS record that identifies a key in the child zone; the child’s DNSKEY then verifies signatures over its own resource-record sets. The same check repeats until the zone holding the requested answer is reached.
This makes DNSSEC a chain-of-trust system rather than a single signature on the final address. A broken parent-to-child link can make otherwise well-formed records fail validation. During a key rollover, operators coordinate the child DNSKEY, parent DS and signature publication so that caches do not observe a gap between the old and new trust paths. The protocol records are observable in DNS messages, but the resolver’s local trust-anchor configuration is part of the validation context too.
DNSKEY, DS, RRSIG and denial records have different jobs
DNSKEY publishes a zone’s public key. DS, stored by the parent, is a digest that links the delegation to a child key. RRSIG carries a signature over a resource-record set and includes inception and expiration times. NSEC and NSEC3 support authenticated denial of existence, allowing a validator to check a signed claim that a name or record type does not exist.
Operators often discuss key-signing and zone-signing roles, but a trace should be interpreted from the actual records and signatures rather than assuming every zone uses the same operational key layout. RFC 4033, RFC 4034 and RFC 4035 define the core service, record formats and protocol changes; RFC 9364 collects the current DNSSEC standards guidance. RFC 5155 specifies NSEC3.
Validation has secure, insecure and bogus outcomes
A validating resolver can classify data as secure when it verifies from a trusted starting point, or insecure when the chain proves that the delegation is unsigned. Bogus means a chain indicates that validation should succeed but one or more required records or signatures fail. Indeterminate means the resolver cannot establish a validation state, for example because it lacks the necessary trust context.
These states explain why an unsigned zone and a broken signed zone should not be treated alike. The first can be returned without DNSSEC authentication; the second may cause a validating resolver to return a failure such as SERVFAIL. When diagnosing an outage, record the resolver, validation state and exact failing delegation rather than simply labeling the domain “DNS is down.”
Authenticated denial proves absence, not a private answer
Negative DNS answers need integrity protection too. An NSEC or NSEC3 proof lets a validator establish that a requested name or record type is absent according to the signed zone. NSEC links ordered names directly and can reveal names in a zone; NSEC3 hashes names to reduce straightforward enumeration, but it is not a general confidentiality mechanism. The signed proof is still public DNS data.
Similarly, a valid RRSIG says that the covered record set can be verified under the DNSSEC trust chain and signature time window. It does not endorse the website’s content, certify that an address is harmless or replace browser TLS identity checks. DNSSEC authenticates DNS data; it is not a website reputation service.
The AD flag depends on trusting the validating resolver
A recursive resolver may perform validation for a stub client and set the Authenticated Data bit when it believes the answer validates. A client that does not validate locally must trust that resolver and the channel used to reach it. If the client cannot trust that relationship, it may need a validating stub or another authenticated channel. An AD bit by itself is not a cryptographic signature that any observer can verify.
When reviewing a packet capture, distinguish the presence of DNSSEC records from proof that the endpoint actually performed validation. Check the client’s resolver settings and whether the query requested DNSSEC records; the resolver’s logs or a local validating tool may be needed to establish the decision.
Diagnose a DNSSEC failure without disabling protection
Start with the failing name and record type, then query the relevant delegations and compare the parent DS with the child DNSKEY. Check for missing or stale DS records, expired or not-yet-valid RRSIG records, unsupported algorithms, incomplete negative proofs and clock errors on validators. Compare results from more than one validating resolver to separate a zone publication problem from one resolver’s cache or configuration.
A diagnostic query that asks a resolver to return data without its normal checking can help isolate a validation failure, but it is not a safe permanent workaround. Capture the exact records and timestamps, report the failing link, and restore normal validation. Protocol Explorer explains a simplified signed-answer path; it does not validate live DNS records.
Explore DNSSEC interactively
Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.
Specification and source
For exact protocol requirements, consult the primary document: RFC 4033: DNS Security Introduction and Requirements. This page summarizes selected behavior and is not a substitute for the specification.
Related protocol lessons
Browse all security and access protocols · What encryption and DNSSEC each protect