<?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 blog.luescher.io</title><link>https://blog.luescher.io/tags/infrastructure-as-code/</link><description>Recent content in Infrastructure-as-Code on blog.luescher.io</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Stephan Lüscher</copyright><lastBuildDate>Tue, 30 Jun 2026 23:56:33 +0200</lastBuildDate><atom:link href="https://blog.luescher.io/tags/infrastructure-as-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Manage DNS as Code with Infrahub and DNSControl</title><link>https://blog.luescher.io/2026/06/manage-dns-as-code-with-infrahub-and-dnscontrol/</link><pubDate>Tue, 30 Jun 2026 17:05:37 +0200</pubDate><guid>https://blog.luescher.io/2026/06/manage-dns-as-code-with-infrahub-and-dnscontrol/</guid><description>&lt;p&gt;Managing DNS across multiple providers can easily become a headache. By combining
&lt;a href="https://opsmill.com/infrahub-platform/" target="_blank" rel="noreferrer"&gt;InfraHub&lt;/a&gt; and
&lt;a href="https://docs.dnscontrol.org/" target="_blank" rel="noreferrer"&gt;DNSControl&lt;/a&gt;, you can finally define your DNS as code, with a
single source of truth, peer review, and zero manual syncs.&lt;/p&gt;
&lt;p&gt;To bridge these tools, I created
&lt;a href="https://codeberg.org/tepene/infrahub-dnscontrol" target="_blank" rel="noreferrer"&gt;infrahub-dnscontrol&lt;/a&gt;, a repository providing
the schema, Jinja2 templates, and configurations needed to connect them. The workflow is simple:
define your DNS data in InfraHub, use Jinja2 transforms to generate DNSControl artifacts, and
manage your registrars, zones, and records across platforms, all from that single source of
truth.&lt;/p&gt;</description></item></channel></rss>