<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Forwarder on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/forwarder/</link>
    <description>Recent content in Forwarder 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/forwarder/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DNS Caching Forwarders: dnsmasq vs Knot Resolver vs Unbound (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-21-self-hosted-dns-caching-forwarders-dnsmasq-knot-resolver-unbound-guide/</link>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-21-self-hosted-dns-caching-forwarders-dnsmasq-knot-resolver-unbound-guide/</guid>
      <description>&lt;p&gt;A DNS caching forwarder sits between your local network and upstream resolvers, storing query results locally to reduce latency, lower bandwidth usage, and improve reliability. Unlike full recursive resolvers that perform the complete DNS resolution chain from root servers downward, caching forwarders delegate recursion to upstream providers while maintaining a local cache of recent answers.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
