<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dane on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/dane/</link>
    <description>Recent content in Dane on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 21 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/dane/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DNS TLSA/DANE Management: hash-slinger vs ldns vs Knot DNS</title>
      <link>https://www.pistack.xyz/posts/2026-05-21-self-hosted-dns-tlsa-dane-management-hash-slinger-ldns-knot-guide/</link>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-21-self-hosted-dns-tlsa-dane-management-hash-slinger-ldns-knot-guide/</guid>
      <description>&lt;p&gt;DANE (DNS-based Authentication of Named Entities) is a protocol that uses DNSSEC-secured TLSA records to associate TLS certificates with domain names. Instead of relying solely on certificate authorities (CAs) for trust validation, DANE allows domain owners to publish certificate fingerprints directly in DNS. This eliminates the risk of rogue CA-issued certificates and gives administrators complete control over TLS trust chains. In this guide, we compare three open-source tools for managing TLSA records and DANE validation: hash-slinger, ldns (with ldns-dane), and Knot DNS.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
