<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dnstap on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/dnstap/</link>
    <description>Recent content in Dnstap on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 03 May 2026 17:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/dnstap/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DNS Logging and Analysis: dnstap, PowerDNS-Admin, and go-dnstap Comparison Guide</title>
      <link>https://www.pistack.xyz/posts/2026-05-03-self-hosted-dns-logging-analysis-dnstap-powerdns-knot-guide/</link>
      <pubDate>Sun, 03 May 2026 17:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-03-self-hosted-dns-logging-analysis-dnstap-powerdns-knot-guide/</guid>
      <description>&lt;p&gt;DNS logging and analysis is a critical component of network observability that many self-hosters overlook. While tools like Pi-hole and AdGuard Home focus on blocking and filtering, a dedicated DNS logging pipeline lets you capture every query, analyze traffic patterns, detect anomalies, and maintain audit trails for compliance. This guide compares three approaches to self-hosted DNS logging and analysis: &lt;strong&gt;dnstap-based collectors&lt;/strong&gt;, &lt;strong&gt;PowerDNS-Admin&lt;/strong&gt; for query logging, and &lt;strong&gt;go-dnstap&lt;/strong&gt; for high-performance query capture.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
