<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DNSSEC on The Coders Blog</title><link>https://thecodersblog.com/tag/dnssec/</link><description>Recent content in DNSSEC on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 22:22:12 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/dnssec/index.xml" rel="self" type="application/rss+xml"/><item><title>When DNSSEC Goes Wrong: Responding to the .de TLD Outage</title><link>https://thecodersblog.com/dnssec-incident-response-for-de-tld-2026/</link><pubDate>Wed, 06 May 2026 22:22:12 +0000</pubDate><guid>https://thecodersblog.com/dnssec-incident-response-for-de-tld-2026/</guid><description>&lt;p&gt;Millions of .de domains vanished from the internet on May 5, 2026, not due to a sophisticated attack, but a seemingly routine DNSSEC key rotation gone awry. DENIC, the registry for Germany&amp;rsquo;s country-code top-level domain, inadvertently published incorrect DNSSEC signatures, triggering widespread SERVFAIL errors on validating resolvers worldwide. For users of services like Cloudflare&amp;rsquo;s 1.1.1.1, this meant the .de TLD effectively ceased to exist for several agonizing hours.&lt;/p&gt;
&lt;h3 id="the-core-problem-broken-signatures-broken-resolution"&gt;The Core Problem: Broken Signatures, Broken Resolution&lt;/h3&gt;
&lt;p&gt;The incident stemmed from a faulty Zone Signing Key (ZSK) rotation. During this process, DENIC’s system introduced malformed RRSIG records for the .de zone. Specifically, the ZSK tag 33834 was found on an NSEC3 record, a configuration that, when combined with other factors in the validation chain, broke the cryptographic trust model. When a validating resolver queried for a .de domain, it received these flawed signatures, leading it to conclude the DNS data was untrustworthy and respond with SERVFAIL. This &amp;ldquo;fail-closed&amp;rdquo; nature of DNSSEC, while intended to prevent spoofing, directly translated operational errors into complete service unavailability.&lt;/p&gt;</description></item><item><title>DNSSEC Outage Disrupts .de Domains, Now Resolved</title><link>https://thecodersblog.com/dnssec-disruption-affecting-de-domains-2026/</link><pubDate>Wed, 06 May 2026 17:00:05 +0000</pubDate><guid>https://thecodersblog.com/dnssec-disruption-affecting-de-domains-2026/</guid><description>&lt;p&gt;Hundreds of thousands of .de domains suddenly became unreachable on May 5, 2026, not due to a massive denial-of-service attack or a widespread network failure, but a single misconfiguration in the Domain Name System Security Extensions (DNSSEC) implementation at DENIC eG, the registry for Germany&amp;rsquo;s country-code top-level domain. For several hours, users relying on validating DNS resolvers encountered frustrating &lt;code&gt;SERVFAIL&lt;/code&gt; errors, effectively rendering a significant portion of the German internet invisible. This incident serves as a stark, albeit temporary, reminder of the inherent complexities and critical fragility underlying our internet&amp;rsquo;s security infrastructure.&lt;/p&gt;</description></item><item><title>.de TLD Offline: DNSSEC Vulnerabilities Expose Infrastructure Weaknesses</title><link>https://thecodersblog.com/de-tld-dnssec-outage-analysis-2026/</link><pubDate>Wed, 06 May 2026 03:34:18 +0000</pubDate><guid>https://thecodersblog.com/de-tld-dnssec-outage-analysis-2026/</guid><description>&lt;p&gt;The internet ground to a halt for legions of &lt;code&gt;.de&lt;/code&gt; domain users around May 5, 2026. Not due to a widespread BGP incident or a distributed denial-of-service attack, but a self-inflicted wound emanating from the heart of Domain Name System Security Extensions (DNSSEC) implementation. A botched key rollover by DENIC, the registry for the &lt;code&gt;.de&lt;/code&gt; top-level domain, effectively severed the chain of trust for millions of users relying on validating DNS resolvers.&lt;/p&gt;</description></item></channel></rss>