<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ldns on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/ldns/</link>
    <description>Recent content in Ldns on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/ldns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DNSSEC Key Management: dnssec-keygen vs ldns-keygen vs Knot DNS keymgr</title>
      <link>https://www.pistack.xyz/posts/2026-06-02-dnssec-key-management-dnssec-keygen-ldns-keygen-knot-keymgr-guide/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-02-dnssec-key-management-dnssec-keygen-ldns-keygen-knot-keymgr-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;DNSSEC protects DNS responses from forgery by cryptographically signing zone data. But the operational challenge isn&amp;rsquo;t the signing itself — it&amp;rsquo;s &lt;strong&gt;key management&lt;/strong&gt;. Generating, rotating, and revoking DNSSEC keys securely is critical: a compromised ZSK can poison an entire domain&amp;rsquo;s cache, and misconfigured KSK rollovers can make your zone unreachable. This article compares three battle-tested DNSSEC key management toolchains: &lt;strong&gt;dnssec-keygen&lt;/strong&gt; (BIND), &lt;strong&gt;ldns-keygen&lt;/strong&gt; (NLnet Labs), and &lt;strong&gt;keymgr&lt;/strong&gt; (Knot DNS).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
