Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is DNSSEC?

DNSSEC signs DNS data so a resolver can prove an answer came from the real zone and was not altered. It authenticates records; it does not keep them private.

Illustration for the cybersecurity term DNSSEC
Home / Blog / Cybersecurity Terms / What Is DNSSEC?
17 November 2026

What Is DNSSEC?

What Is DNSSEC?

The original DNS specification contains no way to tell a genuine answer from a forged one. A resolver accepts whatever arrives first with a matching transaction identifier, which is why cache poisoning worked for so long. DNS Security Extensions, defined across RFCs 4033, 4034, and 4035, add origin authentication and integrity: the zone owner signs the records, and a validating resolver checks those signatures against a chain of trust that leads back to the root.

The Records Involved

The chain runs from the root zone, whose key is distributed with resolver software and ceremonially managed by ICANN, down through .uk, to example.co.uk. A validating resolver walks that chain and returns the Authenticated Data flag when every link verifies. If a signature is wrong or missing where it should be present, the resolver returns SERVFAIL rather than the answer — the failure mode is unavailability, not silent acceptance.

What It Does Not Do

Two misconceptions cause most of the disappointment. DNSSEC provides no confidentiality: responses are signed, not encrypted, so an observer reads them exactly as before. That is the job of DoT or DoH, and the two are complementary.

It also protects the data, not the last hop. Validation normally happens at the recursive resolver, so the path from resolver to client remains unprotected unless the client validates for itself or the link is encrypted. And a signed zone containing a record pointing at an attacker-controlled host is still signed correctly — DNSSEC proves authenticity of the data, not the wisdom of it.

NSEC originally allowed zone walking, since each record names the next existing one. NSEC3 hashes those names, and NSEC3 with opt-out or the newer white-lies technique reduces the exposure further, though offline dictionary attacks against NSEC3 hashes are feasible for guessable names.

Operational Reality

DNSSEC fails loudly. A zone whose signatures expire goes dark for every validating resolver on the internet, and this has happened to significant organisations. The 2012 and 2015 incidents involving expired signatures at national registries, and the SERVFAIL events that have affected individual banks and government bodies, all traced to the same cause: signatures have an expiry, and automation that renews them must never stop.

Key rollover is the other hazard. Changing a zone signing key is contained within your zone and is safely automated. Changing a key signing key requires the parent’s DS record to be updated at the registrar in step with your own change, and getting the order or the timing wrong breaks resolution. Use a double-signature or pre-publish rollover with waits longer than the relevant time-to-live, and verify with external tooling such as DNSViz or Verisign’s analyser before removing anything.

The root key signing key was itself rolled on 11 October 2018, the first time since the root was signed in 2010, which was a useful demonstration that the model scales.

Is It Worth Deploying?

For most organisations the honest answer is: yes, and increasingly so, because other controls now depend on it. DANE for SMTP is meaningless without it. UK public sector guidance expects it, and .gov.uk domains are signed. Modern DNS platforms from the major cloud providers and from most UK registrars offer one-click signing with automated key management, which removes nearly all of the operational risk that justified the hesitation ten years ago.

If you run your own authoritative servers, treat signature expiry and DS synchronisation as monitored production dependencies with alerting, not as a configuration you set once. Our Infrastructure and Architecture Review Services include DNSSEC validation and key lifecycle review.

FAQ – Frequently Asked Questions

Does DNSSEC Encrypt DNS Traffic?

No. DNSSEC signs records so a resolver can verify they are authentic and unmodified, but the responses travel in plaintext and anyone on the path can read them. Confidentiality requires DNS over TLS or DNS over HTTPS. The two mechanisms address different threats and are designed to be used together rather than as alternatives.

What Happens If My DNSSEC Signatures Expire?

Every validating resolver returns SERVFAIL for your domain, which means your websites, email, and anything else depending on those names become unreachable for a large share of the internet. There is no graceful degradation. Signature re-signing must be automated and monitored with alerting well before expiry, and expiry dates should be tracked like certificate expiry.

Do I Need to Change Registrar to Enable DNSSEC?

Not usually. Most UK registrars and all the major cloud DNS platforms support publishing DS records and offer managed signing. Check that your registrar can submit DS records to the registry for your top-level domain, since that is the link that completes the chain of trust. If it cannot, that is a reasonable reason to move.

Does DNSSEC Stop Domain Hijacking?

Not by itself. If an attacker takes over your registrar account, they can replace the nameservers and the DS record together, producing a correctly signed zone under their control. DNSSEC prevents tampering in transit and cache poisoning. Protecting the registrar account with strong authentication and registry lock addresses the hijacking case.

Related Terms

You May Be Interested In These

What Is Spear Phishing?

Cybersecurity Terms

17 November 2026

What Is Spear Phishing?

Read More
What Is Certificate Transparency?

Cybersecurity Terms

17 November 2026

What Is Certificate Transparency?

Read More
What Is YARA-X?

Cybersecurity Terms

17 November 2026

What Is YARA-X?

Read More