<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on 5ok — sysadmin, devops, hosting</title><link>https://www.5ok.eu/tags/git/</link><description>Recent content in Git on 5ok — sysadmin, devops, hosting</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.5ok.eu/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing DNS Zones as Code</title><link>https://www.5ok.eu/blog/managing-dns-zones-as-code/</link><pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.5ok.eu/blog/managing-dns-zones-as-code/</guid><description>&lt;p&gt;If you run more than a handful of domains, you know the drill: log into a web console, find the right zone, add a record, hope you didn&amp;rsquo;t typo a hostname. There&amp;rsquo;s no history of who changed what, no review before it goes live, and no undo if it breaks production.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s exactly the gap dnscontrol and git close.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://docs.dnscontrol.org/"&gt;dnscontrol&lt;/a&gt; solves this by treating DNS zones as code: you describe your records declaratively in JavaScript configuration files, commit them to git, and let a tool compute and apply the diff against your actual DNS provider(s). It&amp;rsquo;s the same idea as infrastructure-as-code applied to DNS specifically.&lt;/p&gt;</description></item></channel></rss>