<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Knot-Dns on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/knot-dns/</link>
    <description>Recent content in Knot-Dns on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 13 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/knot-dns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DNS Redirect Servers: dnsmasq vs Knot DNS vs PowerDNS Recursor</title>
      <link>https://www.pistack.xyz/posts/2026-05-13-self-hosted-dns-redirect-servers-dnsmasq-knot-dns-powerdns-recursor-guide/</link>
      <pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-13-self-hosted-dns-redirect-servers-dnsmasq-knot-dns-powerdns-recursor-guide/</guid>
      <description>&lt;p&gt;DNS redirect servers intercept and rewrite DNS queries to route traffic to specific endpoints, enforce content policies, or implement custom routing rules. Whether you need to redirect internal services to private IPs, block malicious domains, or implement split-horizon DNS, the right DNS redirect server is a cornerstone of self-hosted infrastructure. This guide compares &lt;strong&gt;dnsmasq&lt;/strong&gt;, &lt;strong&gt;Knot DNS&lt;/strong&gt;, and &lt;strong&gt;PowerDNS Recursor&lt;/strong&gt; for DNS redirect use cases.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
