<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dns-as-Code on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/dns-as-code/</link>
    <description>Recent content in Dns-as-Code 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/dns-as-code/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DNS Zone Provisioning: DNSControl vs OctoDNS vs Lexicon (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-13-self-hosted-dns-zone-provisioning-dnscontrol-octodns-lexicon-guide/</link>
      <pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-13-self-hosted-dns-zone-provisioning-dnscontrol-octodns-lexicon-guide/</guid>
      <description>&lt;p&gt;Managing DNS zones across multiple providers &amp;ndash; Cloudflare, AWS Route 53, Google Cloud DNS, or self-hosted BIND/PowerDNS &amp;ndash; is one of the most error-prone tasks in infrastructure operations. Manual changes through web consoles lead to typos, forgotten records, and inconsistent state. DNS-as-Code solves this by treating zone files as version-controlled configuration, deployed through CI/CD pipelines with automatic validation and rollback.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
