OOmnistu

Blog / Security

Security

DNSSEC explained: signed DNS answers and the chain of trust

DNSSEC signs DNS data so resolvers can verify where an answer came from and that it arrived intact - RRSIG, DNSKEY, DS, and why authenticity is not privacy.

OOmnistu
Reviewed 2026-11-20 · 3 min read

DNSSEC - the DNS Security Extensions - is specified in RFCs 4033, 4034 and 4035, along with a handful of other documents that RFC 9364 gathers in one place. RFC 9364 also states that using DNSSEC for origin authentication of DNS data is the best current practice. This guide covers what the extensions add, what they deliberately do not add, and how the authentication chain fits together.

What DNSSEC provides

Per RFC 4033, the DNS security extensions provide origin authentication and integrity protection for DNS data, as well as a means of public key distribution. In practice, that means a validating resolver can check that an answer really came from the zone's authoritative data and was not altered on the way. DNSSEC does this by associating cryptographically generated digital signatures with DNS record sets; those signatures are stored in a dedicated record type, the RRSIG record.

What it does not provide

The same document is explicit about the limits: the extensions do not provide confidentiality. DNSSEC is not designed to hide DNS data, to give different answers to different inquirers, or to protect against denial of service attacks. It authenticates data; it does not encrypt it. If you need to keep DNS queries private from a network observer, that is a separate problem with separate mechanisms.

The records and the chain of trust

Besides RRSIG for signatures, DNSSEC stores a zone's public keys in DNSKEY records, and links a child zone to its parent with DS - delegation signer - records. A validating resolver starts from a trust anchor - a configured DNSKEY record or a hash of one, typically at the DNS root - and builds the authentication chain down to the answer. The typical chain runs DNSKEY, then zero or more DS-to-DNSKEY steps through each delegation, then the signed record set itself. DNSSEC can also prove that a name or record type does not exist, through authenticated denial of existence with NSEC records (and the NSEC3 variant).

The calm version

DNSSEC signs DNS data so resolvers can verify who an answer came from and that it arrived intact - RRSIG for signatures, DNSKEY for public keys, DS to link each zone to its parent, and a trust anchor at the top. It proves authenticity, not privacy, and current best practice says to use it for origin authentication.

Sources: RFC 4033, DNS Security Introduction and Requirements (IETF, March 2005; rfc-editor.org/rfc/rfc4033, fetched 2026-11-20): services provided (origin authentication, integrity, public key distribution), services not provided (no confidentiality, no denial-of-service protection), RRSIG/DNSKEY/DS roles, the authentication chain, authenticated denial of existence. RFC 9364, DNS Security Extensions (DNSSEC) (IETF, February 2023; rfc-editor.org/rfc/rfc9364, fetched 2026-11-20): the RFC 4033-4035 document set and the best-current-practice statement for origin authentication of DNS data.

Frequently asked questions

What is DNSSEC?

The DNS Security Extensions, specified in RFCs 4033, 4034 and 4035: they add origin authentication and integrity protection to DNS data through digital signatures stored in RRSIG records.

Does DNSSEC encrypt DNS traffic?

No. RFC 4033 states the extensions do not provide confidentiality - DNSSEC authenticates data but does not encrypt it, and it is not designed to protect against denial of service attacks.

What are RRSIG, DNSKEY and DS records?

RRSIG stores the digital signatures over DNS record sets, DNSKEY stores a zone's public keys, and DS (delegation signer) links a child zone to its parent so a resolver can build the authentication chain from a trust anchor down to the answer.

Is DNSSEC a current best practice?

Yes for origin authentication: RFC 9364, the IETF's single-reference document for DNSSEC, states that using DNSSEC for origin authentication of DNS data is the best current practice.