<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure-as-Code on Pi Stack</title><link>https://www.pistack.xyz/tags/infrastructure-as-code/</link><description>Recent content in Infrastructure-as-Code on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 21 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/infrastructure-as-code/index.xml" rel="self" type="application/rss+xml"/><item><title>OctoDNS vs DNSControl vs Lexicon: DNS-as-Code Management Guide 2026</title><link>https://www.pistack.xyz/posts/octodns-vs-dnscontrol-vs-lexicon-self-hosted-dns-as-code-guide-2026/</link><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/octodns-vs-dnscontrol-vs-lexicon-self-hosted-dns-as-code-guide-2026/</guid><description>&lt;p>Managing DNS records through provider web consoles is error-prone, unversioned, and impossible to audit. DNS-as-Code tools solve this by treating your DNS zones like infrastructure — defined in version-controlled configuration files, deployed through CI/CD pipelines, and rollbackable with a single commit.&lt;/p></description></item></channel></rss>