Technology1 min read

Restating the case for DNSSEC

By · Published by Everything Blog

In short

The comprehensive review addresses common misconceptions that have stalled broader adoption, including unfounded fears regarding state-level censorship and complaints over protocol complexity. Jantzen points out that government restrictions function through separate legal mechanisms rather than cryptographic domain validation. Her findings also evaluate the IANIX outage tracking list, emphasizing that prolonged deployment cycles are standard for foundational protocols like IPv6. Ultimately, more than 60 internet infrastructure experts and organizations endorsed the paper's findings.

Key points

  • Transport Layer Security cannot guarantee domain authenticity without underlying protecti…: Transport Layer Security cannot guarantee domain authenticity without underlying protections against resolution tampering and homograph attacks.
  • Slow global deployment timelines reflect standard multi-year transition periods previousl…: Slow global deployment timelines reflect standard multi-year transition periods previously observed with protocols like IPv6 and RPKI.
  • The protocol provides essential foundational support for critical downstream security sta…: The protocol provides essential foundational support for critical downstream security standards such as DANE and CAA/TLS.

Sources checked by our analysis pipeline: 1

At CircleID, Barbara Jantzen from deSEC has written a detailed review of the issues surrounding DNSSEC deployment. We’ve heard from deSEC before at APNIC, with Peter Thomassen presenting twice on PING, once on key drift between parent and child, and again on post-quantum cryptography in DNSSEC.

Barbara’s post reviews common myths and misconceptions about DNSSEC. She examines its complexity, role, and broader social utility. A significant part of the discussion centres on the IANIX list, an actively maintained record of DNSSEC-related outages across the namespace.

A persistent line of reasoning argues that because website security is delivered through the TLS certificate used in an HTTP connection, DNSSEC adds little or no value. This could not be further from the truth. Before a browser can validate a TLS certificate, it must first resolve the destination name through DNS. DNS is part of the path to the endpoint that presents the certificate.

If an intermediary can redirect that DNS query, the user may be sent somewhere else entirely. Unless certificate pinning is strongly enforced, an adversary could still establish a certificate authority-backed…

Technology