<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Unbound on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/unbound/</link>
    <description>Recent content in Unbound on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/unbound/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DNS TTL Optimization and Cache Tuning: Unbound vs PowerDNS vs Knot Resolver (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-11-self-hosted-dns-ttl-optimization-cache-tuning-unbound-powerdns-knot-guide/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-11-self-hosted-dns-ttl-optimization-cache-tuning-unbound-powerdns-knot-guide/</guid>
      <description>&lt;p&gt;DNS Time-To-Live (TTL) values determine how long recursive resolvers cache query results. Getting TTL values right is one of the most impactful yet overlooked aspects of DNS infrastructure optimization. Too short, and you generate excessive upstream queries; too long, and clients receive stale data when records change.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
