<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dns-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/dns-management/</link>
    <description>Recent content in Dns-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 03 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/dns-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DNS Split-View Traffic Management: BIND Views vs PowerDNS LUA Records vs Knot DNS Response Policy</title>
      <link>https://www.pistack.xyz/posts/2026-06-03-self-hosted-dns-split-view-bind-powerdns-knot-guide/</link>
      <pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-03-self-hosted-dns-split-view-bind-powerdns-knot-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;DNS split-view (also known as split-horizon DNS or DNS views) is a technique where a single DNS server returns different answers depending on the client&amp;rsquo;s source IP address or network location. This is essential for organizations that need to serve internal IP addresses to internal clients while presenting public-facing addresses to external queries. Whether you are running a corporate intranet with private service endpoints, managing multi-tenant DNS hosting, or implementing geo-aware DNS routing, split-view DNS gives you fine-grained control over DNS responses.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
