DNSSEC
What is DNSSEC?
DNSSEC adds cryptographic signatures to DNS records so a validating resolver can confirm a response really came from a domain's authoritative owner and was not forged or altered in transit. AdminKit's DNS Lookup tool shows a domain's DNSKEY, RRSIG and DS records that make up its DNSSEC chain.
By AdminKit team, Netbase JSC · Updated
DNSSEC (Domain Name System Security Extensions) adds cryptographic signatures to DNS records so a validating resolver can confirm a response actually came from a domain’s authoritative owner and wasn’t forged or altered in transit. It works by chaining trust from the DNS root down through each parent zone to the domain’s own signed records (RRSIG, DNSKEY, and DS records tie the chain together), so a resolver can verify authenticity without a prior trust relationship with that domain. The DS record specifically is what lets that chain cross from a parent zone into a child zone it doesn’t otherwise trust. Plain DNS has no such protection, which is what makes cache-poisoning and spoofing attacks possible — DNSSEC closes that gap, though it guarantees authenticity, not confidentiality, since responses are still sent in the clear. NIST’s Secure Domain Name System (DNS) Deployment Guide, SP 800-81-2, frames DNS security the same way: because DNS data is meant to be public, its primary security goals are data integrity and source authentication. Adoption needs both the domain’s DNS provider to sign the zone and the client’s resolver to actually validate signatures, so a signed domain can still get unvalidated answers from a resolver that ignores DNSSEC. The DNSSEC specification itself is split across RFC 4033 (introduction and requirements) and RFC 4034 (the DNSKEY, RRSIG and DS resource record formats); the signing algorithms a zone can use are tracked in IANA’s DNSSEC Algorithm Numbers registry. AdminKit’s DNSSEC check tool runs a live query against a validating resolver and reports a domain’s secure/insecure/bogus verdict directly, rather than only showing the raw records.
Frequently asked questions
Does DNSSEC encrypt DNS traffic?
No -- DNSSEC guarantees authenticity, confirming a response really came from the domain's authoritative owner and wasn't altered, but it doesn't guarantee confidentiality; responses are still sent in the clear.
If a domain has DNSSEC enabled, am I automatically protected?
Not necessarily -- DNSSEC needs both the domain's DNS provider to sign the zone and the client's resolver to actually validate signatures, so a signed domain can still return unvalidated answers to a resolver that ignores DNSSEC.
What does the DS record do in a DNSSEC chain?
The DS record is what lets the chain of trust cross from a parent zone into a child zone it doesn't otherwise trust, linking the two zones' signing keys together.
What attack does DNSSEC actually prevent?
DNSSEC closes the gap that makes cache-poisoning and DNS spoofing possible, since a validating resolver can detect a forged or altered response instead of trusting whatever it receives.
Sources
- RFC 4033 -- DNS Security Introduction and Requirements
- RFC 4034 -- Resource Records for the DNS Security Extensions
- IANA -- Domain Name System Security (DNSSEC) Algorithm Numbers registry
- ICANN -- DNSSEC: What Is It and Why Is It Important?
- NIST SP 800-81-2 -- Secure Domain Name System (DNS) Deployment Guide