<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>ExternalDNS | A DevOps Blog</title><link>https://blog.bsdserver.nl/tag/external-dns/</link><description>Hands-on DevOps and homelab content: Kubernetes clusters, self-hosted services, CI/CD pipelines and infrastructure as code, by Patrick de Ruiter of We Build Your Cloud.</description><language>en</language><image><url>https://blog.bsdserver.nl/images/app-icon.svg</url><title>A DevOps Blog</title><link>https://blog.bsdserver.nl/</link></image><lastBuildDate>Wed, 18 Nov 2026 09:00:00 +0100</lastBuildDate><atom:link href="https://blog.bsdserver.nl/tag/external-dns/rss/" rel="self" type="application/rss+xml"/><ttl>60</ttl><item><title>Integrating Kubernetes External-DNS with BIND for Automatic DNS Management</title><link>https://blog.bsdserver.nl/integrating-kubernetes-external-dns-with-bind-for-automatic-dns-management/</link><guid isPermaLink="false">693b6cfc79eb54000160a575</guid><dc:creator>Patrick de Ruiter</dc:creator><pubDate>Fri, 12 Dec 2025 01:16:44 +0000</pubDate><description>External-DNS is a Kubernetes controller that automatically creates and manages DNS records based on Kubernetes resources like Services and Ingresses.</description><category>BIND</category><category>DNS</category><category>Kubernetes</category><category>ExternalDNS</category><category>Automation</category><media:content url="https://blog.bsdserver.nl/content/images/2026/01/bind-k8s-external-dns.png" medium="image"/><content:encoded><![CDATA[<p>External-DNS is a Kubernetes controller that automatically creates and manages DNS records based on Kubernetes resources like Services and Ingresses. Without it, every new service means a manual DNS change, and deleted services leave stale records behind.</p>
<p>When combined with BIND using the RFC2136 (dynamic DNS) provider, you get fully automated DNS management for your Kubernetes workloads without relying on cloud DNS providers. This post sets up the BIND side, deploys External-DNS, and shows how Services, Ingresses and HTTPRoutes become DNS records.</p>
<h2 id="why-external-dns-with-bind">Why External-DNS with BIND? <a class="anchor" data-pagefind-ignore href="#why-external-dns-with-bind" aria-label="Link to this section">#</a></h2>
<ul>
<li><strong>No manual DNS changes</strong>: a hostname annotation or Ingress host is enough.</li>
<li><strong>Cleanup included</strong>: records disappear when the resource is deleted.</li>
<li><strong>Your own DNS</strong>: no cloud DNS provider needed; BIND stays the authority.</li>
<li><strong>Safe sharing</strong>: TXT ownership records keep External-DNS away from records it did not create.</li>
</ul>
<h3 id="when-to-use-it">When to use it <a class="anchor" data-pagefind-ignore href="#when-to-use-it" aria-label="Link to this section">#</a></h3>
<ul>
<li><strong>Use it</strong> for on-premises or homelab clusters with BIND as the authoritative DNS, where services come and go.</li>
<li><strong>Skip it</strong> when your zone is hosted at a cloud DNS provider (use External-DNS&rsquo;s provider for that instead), or for a handful of services that never change.</li>
</ul>
<h2 id="how-external-dns-works">How External-DNS Works <a class="anchor" data-pagefind-ignore href="#how-external-dns-works" aria-label="Link to this section">#</a></h2>
<p>External-DNS watches Kubernetes resources (Services, Ingresses, Gateway API resources) and synchronizes DNS records with an external DNS provider. For BIND, it uses the RFC2136 protocol - the same dynamic DNS update mechanism we covered in <a href="https://blog.bsdserver.nl/setting-up-dynamic-dns-updates-with-bind-and-tsig-authentication/">the previous post</a>.</p>
<table>
	<thead>
			<tr>
					<th>Component</th>
					<th>Runs on</th>
					<th>Job</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>External-DNS</td>
					<td>Kubernetes, one pod</td>
					<td>Watches resources, computes the records they need, sends signed updates.</td>
			</tr>
			<tr>
					<td>TSIG secret</td>
					<td>Kubernetes Secret</td>
					<td>The key External-DNS signs updates with.</td>
			</tr>
			<tr>
					<td>BIND zone (<code>type primary</code>)</td>
					<td>DNS server</td>
					<td>Accepts updates signed with <code>external-dns-key</code>, within its <code>update-policy</code>.</td>
			</tr>
			<tr>
					<td>TXT registry</td>
					<td>In the zone itself</td>
					<td>Marks which records belong to which External-DNS instance.</td>
			</tr>
	</tbody>
</table>
<p>The workflow:</p>
<ol>
<li>You deploy a Service or Ingress with DNS annotations</li>
<li>External-DNS detects the resource and its annotations</li>
<li>External-DNS sends DNS UPDATE requests to your BIND server</li>
<li>BIND creates or updates the DNS records</li>
<li>When resources are deleted, External-DNS removes the corresponding records</li>
</ol>
<h2 id="prerequisites">Prerequisites <a class="anchor" data-pagefind-ignore href="#prerequisites" aria-label="Link to this section">#</a></h2>
<h3 id="bind-configuration">BIND Configuration <a class="anchor" data-pagefind-ignore href="#bind-configuration" aria-label="Link to this section">#</a></h3>
<p>Your BIND server needs to accept dynamic updates. A dedicated key means External-DNS can only touch the zones you grant it. Generate a TSIG key for External-DNS:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">tsig-keygen -a hmac-sha256 external-dns-key &gt; /etc/named/keys/external-dns.key
</span></span></code></pre></div><p>Configure BIND to accept updates. <code>zonesub ANY</code> lets the key change any record in <code>k8s.example.com</code>; the reverse zone only allows PTR records:</p>
<pre tabindex="0"><code>// /etc/named.conf

include &#34;/etc/named/keys/external-dns.key&#34;;

zone &#34;k8s.example.com&#34; {
    type primary;
    file &#34;/var/named/dynamic/k8s.example.com.zone&#34;;
    update-policy {
        grant external-dns-key zonesub ANY;
    };
};

// If managing reverse DNS (External-DNS v0.14 doesn&#39;t create PTR records
// for RFC2136; newer releases have --create-ptr)
zone &#34;1.168.192.in-addr.arpa&#34; {
    type primary;
    file &#34;/var/named/dynamic/192.168.1.rev&#34;;
    update-policy {
        grant external-dns-key zonesub PTR;
    };
};
</code></pre><p>Create the initial zone file. It only needs the SOA and NS records; External-DNS adds the rest. The low TTLs (300) let changes reach clients quickly.</p>
<pre tabindex="0"><code>; /var/named/dynamic/k8s.example.com.zone
$TTL 300
@   IN  SOA ns1.example.com. admin.example.com. (
        2024010101  ; Serial
        3600        ; Refresh
        1800        ; Retry
        604800      ; Expire
        300 )       ; Minimum TTL

    IN  NS  ns1.example.com.
</code></pre><h2 id="deploying-external-dns">Deploying External-DNS <a class="anchor" data-pagefind-ignore href="#deploying-external-dns" aria-label="Link to this section">#</a></h2>
<p>Three pieces: a Secret with the TSIG key, RBAC so External-DNS can read cluster resources, and the Deployment itself.</p>
<h3 id="create-tsig-secret">Create TSIG Secret <a class="anchor" data-pagefind-ignore href="#create-tsig-secret" aria-label="Link to this section">#</a></h3>
<p>First, create a Kubernetes secret containing the TSIG key. Only the secret string goes in; the key name and algorithm are passed as flags.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="c1"># Extract the secret from the key file</span>
</span></span><span class="line"><span class="cl"><span class="nv">TSIG_SECRET</span><span class="o">=</span><span class="k">$(</span>grep secret /etc/named/keys/external-dns.key <span class="p">|</span> cut -d <span class="s1">&#39;&#34;&#39;</span> -f2<span class="k">)</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl">kubectl create namespace external-dns
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl">kubectl create secret generic external-dns-tsig <span class="se">\
</span></span></span><span class="line"><span class="cl">  --namespace external-dns <span class="se">\
</span></span></span><span class="line"><span class="cl">  --from-literal<span class="o">=</span>tsig-secret<span class="o">=</span><span class="s2">&#34;</span><span class="nv">$TSIG_SECRET</span><span class="s2">&#34;</span>
</span></span></code></pre></div><p>Or as a YAML manifest:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">Secret</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns-tsig</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">namespace</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l">Opaque</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">stringData</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">tsig-secret</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;your-base64-tsig-secret-here&#34;</span><span class="w">
</span></span></span></code></pre></div><h3 id="rbac-configuration">RBAC Configuration <a class="anchor" data-pagefind-ignore href="#rbac-configuration" aria-label="Link to this section">#</a></h3>
<p>External-DNS only reads from the Kubernetes API. The ClusterRole grants read access to the resources it can use as sources (Services, Ingresses, Gateway API routes), plus nodes, pods and namespaces it needs to resolve targets and filters.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">ServiceAccount</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">namespace</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nn">---</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">rbac.authorization.k8s.io/v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">ClusterRole</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">rules</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- <span class="nt">apiGroups</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">resources</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;services&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;endpoints&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;pods&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">verbs</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;get&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;watch&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;list&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- <span class="nt">apiGroups</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;extensions&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;networking.k8s.io&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">resources</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;ingresses&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">verbs</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;get&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;watch&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;list&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- <span class="nt">apiGroups</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">resources</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;nodes&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">verbs</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;list&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;watch&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- <span class="nt">apiGroups</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">resources</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;namespaces&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">verbs</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;get&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;watch&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;list&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- <span class="nt">apiGroups</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;gateway.networking.k8s.io&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">resources</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;gateways&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;httproutes&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;tlsroutes&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;tcproutes&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;udproutes&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">verbs</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s2">&#34;get&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;watch&#34;</span><span class="p">,</span><span class="w"> </span><span class="s2">&#34;list&#34;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nn">---</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">rbac.authorization.k8s.io/v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">ClusterRoleBinding</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns-viewer</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">roleRef</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">apiGroup</span><span class="p">:</span><span class="w"> </span><span class="l">rbac.authorization.k8s.io</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">ClusterRole</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">subjects</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">ServiceAccount</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">namespace</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span></code></pre></div><h3 id="external-dns-deployment">External-DNS Deployment <a class="anchor" data-pagefind-ignore href="#external-dns-deployment" aria-label="Link to this section">#</a></h3>
<p>One replica with the <code>Recreate</code> strategy, so two External-DNS pods never update the zone at the same time. The flags are explained in the next section.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">apps/v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">Deployment</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">namespace</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">spec</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">replicas</span><span class="p">:</span><span class="w"> </span><span class="m">1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">strategy</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l">Recreate</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">selector</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">matchLabels</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">app</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">template</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">labels</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">app</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">spec</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">serviceAccountName</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">containers</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">image</span><span class="p">:</span><span class="w"> </span><span class="l">registry.k8s.io/external-dns/external-dns:v0.14.2</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">args</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">source=service</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">source=ingress</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">provider=rfc2136</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">rfc2136-host=192.168.1.10</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">rfc2136-port=53</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">rfc2136-zone=k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">rfc2136-tsig-keyname=external-dns-key</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">rfc2136-tsig-secret-alg=hmac-sha256</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">rfc2136-tsig-axfr</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">domain-filter=k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">policy=sync</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">registry=txt</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">txt-owner-id=k8s-cluster</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">interval=30s</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- --<span class="l">log-level=info</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">env</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">EXTERNAL_DNS_RFC2136_TSIG_SECRET</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">              </span><span class="nt">valueFrom</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">                </span><span class="nt">secretKeyRef</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">                  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns-tsig</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">                  </span><span class="nt">key</span><span class="p">:</span><span class="w"> </span><span class="l">tsig-secret</span><span class="w">
</span></span></span></code></pre></div><h2 id="configuration-options">Configuration Options <a class="anchor" data-pagefind-ignore href="#configuration-options" aria-label="Link to this section">#</a></h2>
<h3 id="key-arguments-explained">Key Arguments Explained <a class="anchor" data-pagefind-ignore href="#key-arguments-explained" aria-label="Link to this section">#</a></h3>
<p><strong>Sources:</strong> which resources External-DNS turns into records.</p>
<ul>
<li><code>--source=service</code> - Watch Kubernetes Services</li>
<li><code>--source=ingress</code> - Watch Ingress resources</li>
<li><code>--source=gateway-httproute</code> - Watch Gateway API HTTPRoutes</li>
</ul>
<p><strong>Provider Settings:</strong> how to reach and authenticate to BIND.</p>
<ul>
<li><code>--provider=rfc2136</code> - Use RFC2136 dynamic DNS</li>
<li><code>--rfc2136-host</code> - BIND server address</li>
<li><code>--rfc2136-port</code> - DNS port. Always set it: the default is <code>0</code>, not 53</li>
<li><code>--rfc2136-zone</code> - Zone to manage</li>
<li><code>--rfc2136-tsig-keyname</code> - TSIG key name (must match BIND config)</li>
<li><code>--rfc2136-tsig-secret-alg</code> - Algorithm (hmac-sha256)</li>
<li><code>--rfc2136-tsig-axfr</code> - Allow zone transfers to read existing records</li>
<li>The TSIG secret itself comes from the <code>EXTERNAL_DNS_RFC2136_TSIG_SECRET</code> environment variable. External-DNS maps every flag to <code>EXTERNAL_DNS_&lt;FLAG&gt;</code>; a plain <code>RFC2136_TSIG_SECRET</code> is ignored and every update fails with <code>dns: bad authentication</code></li>
</ul>
<p><strong>Filtering:</strong> which names and resources are in scope.</p>
<ul>
<li><code>--domain-filter</code> - Only manage records in this domain</li>
<li><code>--namespace</code> - Only watch resources in specific namespace</li>
<li><code>--annotation-filter</code> - Only manage resources with specific annotations</li>
</ul>
<p><strong>Policies:</strong> what External-DNS may do to existing records.</p>
<table>
	<thead>
			<tr>
					<th>Policy</th>
					<th>Creates</th>
					<th>Updates</th>
					<th>Deletes</th>
					<th>Use it for</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><code>--policy=sync</code></td>
					<td>Yes</td>
					<td>Yes</td>
					<td>Yes</td>
					<td>Full sync; records follow the cluster</td>
			</tr>
			<tr>
					<td><code>--policy=upsert-only</code></td>
					<td>Yes</td>
					<td>Yes</td>
					<td>No</td>
					<td>Getting started, or when deletions are risky</td>
			</tr>
			<tr>
					<td><code>--policy=create-only</code></td>
					<td>Yes</td>
					<td>No</td>
					<td>No</td>
					<td>Only create new records</td>
			</tr>
	</tbody>
</table>
<p><strong>Registry:</strong> how ownership is tracked.</p>
<ul>
<li><code>--registry=txt</code> - Use TXT records to track ownership</li>
<li><code>--txt-owner-id</code> - Unique identifier for this External-DNS instance</li>
</ul>
<h3 id="multiple-zones">Multiple Zones <a class="anchor" data-pagefind-ignore href="#multiple-zones" aria-label="Link to this section">#</a></h3>
<p>To manage multiple zones, deploy multiple External-DNS instances or repeat <code>--rfc2136-zone</code> (supported from v0.14.2; v0.14.0 stops with <code>flag 'rfc2136-zone' cannot be repeated</code>). Add a matching <code>--domain-filter</code> for each:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">args</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- --<span class="l">rfc2136-zone=k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- --<span class="l">rfc2136-zone=apps.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- --<span class="l">domain-filter=k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- --<span class="l">domain-filter=apps.example.com</span><span class="w">
</span></span></span></code></pre></div><h2 id="creating-dns-records">Creating DNS Records <a class="anchor" data-pagefind-ignore href="#creating-dns-records" aria-label="Link to this section">#</a></h2>
<p>How External-DNS finds the hostname depends on the source:</p>
<table>
	<thead>
			<tr>
					<th>Source</th>
					<th>Hostname comes from</th>
					<th>Target comes from</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>Service</td>
					<td><code>external-dns.alpha.kubernetes.io/hostname</code> annotation</td>
					<td>The LoadBalancer IP or hostname</td>
			</tr>
			<tr>
					<td>Ingress</td>
					<td><code>spec.rules[].host</code></td>
					<td><code>status.loadBalancer.ingress</code></td>
			</tr>
			<tr>
					<td>HTTPRoute</td>
					<td><code>spec.hostnames</code></td>
					<td>The parent Gateway&rsquo;s address</td>
			</tr>
	</tbody>
</table>
<h3 id="via-services">Via Services <a class="anchor" data-pagefind-ignore href="#via-services" aria-label="Link to this section">#</a></h3>
<p>Use the <code>external-dns.alpha.kubernetes.io/hostname</code> annotation:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">Service</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">my-app</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">annotations</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external-dns.alpha.kubernetes.io/hostname</span><span class="p">:</span><span class="w"> </span><span class="l">myapp.k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">spec</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l">LoadBalancer</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">ports</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">port</span><span class="p">:</span><span class="w"> </span><span class="m">80</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">targetPort</span><span class="p">:</span><span class="w"> </span><span class="m">8080</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">selector</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">app</span><span class="p">:</span><span class="w"> </span><span class="l">my-app</span><span class="w">
</span></span></span></code></pre></div><p>For multiple hostnames, separate them with commas:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">annotations</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external-dns.alpha.kubernetes.io/hostname</span><span class="p">:</span><span class="w"> </span><span class="l">myapp.k8s.example.com,app.k8s.example.com</span><span class="w">
</span></span></span></code></pre></div><p>Set custom TTL:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">annotations</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external-dns.alpha.kubernetes.io/hostname</span><span class="p">:</span><span class="w"> </span><span class="l">myapp.k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external-dns.alpha.kubernetes.io/ttl</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;60&#34;</span><span class="w">
</span></span></span></code></pre></div><h3 id="via-ingress">Via Ingress <a class="anchor" data-pagefind-ignore href="#via-ingress" aria-label="Link to this section">#</a></h3>
<p>External-DNS automatically uses Ingress hostnames; no annotation needed:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">networking.k8s.io/v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">Ingress</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">my-app-ingress</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">spec</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">ingressClassName</span><span class="p">:</span><span class="w"> </span><span class="l">nginx</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">rules</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">host</span><span class="p">:</span><span class="w"> </span><span class="l">myapp.k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">http</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">paths</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="nt">path</span><span class="p">:</span><span class="w"> </span><span class="l">/</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">pathType</span><span class="p">:</span><span class="w"> </span><span class="l">Prefix</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">backend</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">              </span><span class="nt">service</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">                </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">my-app</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">                </span><span class="nt">port</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">                  </span><span class="nt">number</span><span class="p">:</span><span class="w"> </span><span class="m">80</span><span class="w">
</span></span></span></code></pre></div><p>The Ingress controller must populate the <code>status.loadBalancer.ingress</code> field for External-DNS to determine the target IP.</p>
<h3 id="via-gateway-api">Via Gateway API <a class="anchor" data-pagefind-ignore href="#via-gateway-api" aria-label="Link to this section">#</a></h3>
<p>With Gateway API, External-DNS reads hostnames from HTTPRoute resources. This needs <code>--source=gateway-httproute</code>, which the Deployment above does not set.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">gateway.networking.k8s.io/v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">HTTPRoute</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">my-app-route</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">spec</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">parentRefs</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">my-gateway</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">hostnames</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">myapp.k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">rules</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">matches</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">path</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l">PathPrefix</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">value</span><span class="p">:</span><span class="w"> </span><span class="l">/</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">backendRefs</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">my-app</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">port</span><span class="p">:</span><span class="w"> </span><span class="m">80</span><span class="w">
</span></span></span></code></pre></div><h2 id="record-types">Record Types <a class="anchor" data-pagefind-ignore href="#record-types" aria-label="Link to this section">#</a></h2>
<p>External-DNS picks the record type from the target: an IP gives an A record, a hostname a CNAME.</p>
<h3 id="a-records">A Records <a class="anchor" data-pagefind-ignore href="#a-records" aria-label="Link to this section">#</a></h3>
<p>Created automatically for LoadBalancer Services with external IPs:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">Service</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">my-app</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">annotations</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external-dns.alpha.kubernetes.io/hostname</span><span class="p">:</span><span class="w"> </span><span class="l">myapp.k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">spec</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">type</span><span class="p">:</span><span class="w"> </span><span class="l">LoadBalancer</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">loadBalancerIP</span><span class="p">:</span><span class="w"> </span><span class="m">192.168.1.100</span><span class="w">  </span><span class="c"># Optional: request specific IP</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">ports</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">port</span><span class="p">:</span><span class="w"> </span><span class="m">80</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">selector</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">app</span><span class="p">:</span><span class="w"> </span><span class="l">my-app</span><span class="w">
</span></span></span></code></pre></div><h3 id="cname-records">CNAME Records <a class="anchor" data-pagefind-ignore href="#cname-records" aria-label="Link to this section">#</a></h3>
<p>For services behind cloud load balancers that return hostnames. The <code>target</code> annotation overrides the target External-DNS would otherwise use:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">annotations</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external-dns.alpha.kubernetes.io/hostname</span><span class="p">:</span><span class="w"> </span><span class="l">myapp.k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external-dns.alpha.kubernetes.io/target</span><span class="p">:</span><span class="w"> </span><span class="l">elb.amazonaws.com</span><span class="w">
</span></span></span></code></pre></div><h3 id="txt-records">TXT Records <a class="anchor" data-pagefind-ignore href="#txt-records" aria-label="Link to this section">#</a></h3>
<p>External-DNS creates TXT records to track ownership. It only changes or deletes records whose TXT record carries its own <code>--txt-owner-id</code>:</p>
<pre tabindex="0"><code>myapp.k8s.example.com.    0  IN  A    192.168.1.100
myapp.k8s.example.com.    0  IN  TXT  &#34;heritage=external-dns,external-dns/owner=k8s-cluster,external-dns/resource=service/default/my-app&#34;
a-myapp.k8s.example.com.  0  IN  TXT  &#34;heritage=external-dns,external-dns/owner=k8s-cluster,external-dns/resource=service/default/my-app&#34;
</code></pre><p>Without a <code>ttl</code> annotation the records get TTL 0. The <code>a-</code> record is the newer per-record-type ownership format, written next to the old one.</p>
<p>This prevents External-DNS from accidentally modifying records it didn&rsquo;t create.</p>
<h2 id="advanced-configuration">Advanced Configuration <a class="anchor" data-pagefind-ignore href="#advanced-configuration" aria-label="Link to this section">#</a></h2>
<h3 id="multiple-clusters">Multiple Clusters <a class="anchor" data-pagefind-ignore href="#multiple-clusters" aria-label="Link to this section">#</a></h3>
<p>When multiple clusters share a zone, use different owner IDs. Each cluster then only manages its own records. A per-cluster <code>--txt-prefix</code> keeps their TXT records apart.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="c"># Cluster 1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">args</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- --<span class="l">txt-owner-id=cluster-prod</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- --<span class="l">txt-prefix=_edns-prod-</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="c"># Cluster 2</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">args</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- --<span class="l">txt-owner-id=cluster-staging</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- --<span class="l">txt-prefix=_edns-staging-</span><span class="w">
</span></span></span></code></pre></div><h3 id="filtering-by-annotation">Filtering by Annotation <a class="anchor" data-pagefind-ignore href="#filtering-by-annotation" aria-label="Link to this section">#</a></h3>
<p>Opt-in mode: External-DNS ignores every resource without the annotation. Useful when not every Service should be in DNS.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">args</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- --<span class="l">annotation-filter=external-dns.alpha.kubernetes.io/enabled=true</span><span class="w">
</span></span></span></code></pre></div><p>Then annotate resources explicitly:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">annotations</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external-dns.alpha.kubernetes.io/enabled</span><span class="p">:</span><span class="w"> </span><span class="s2">&#34;true&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external-dns.alpha.kubernetes.io/hostname</span><span class="p">:</span><span class="w"> </span><span class="l">myapp.k8s.example.com</span><span class="w">
</span></span></span></code></pre></div><h3 id="namespace-filtering">Namespace Filtering <a class="anchor" data-pagefind-ignore href="#namespace-filtering" aria-label="Link to this section">#</a></h3>
<p>Limit External-DNS to a specific namespace. <code>--namespace</code> takes a single value (repeating it fails with <code>flag 'namespace' cannot be repeated</code>), so run one instance per namespace if you need several:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">args</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span>- --<span class="l">namespace=production</span><span class="w">
</span></span></span></code></pre></div><h3 id="internal-vs-external-records">Internal vs External Records <a class="anchor" data-pagefind-ignore href="#internal-vs-external-records" aria-label="Link to this section">#</a></h3>
<p>Run two External-DNS instances for split-horizon DNS. Each points at its own BIND server and zone, and the <code>internal</code> annotation decides which instance handles a resource:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="c"># Internal DNS (for internal services)</span><span class="w">
</span></span></span><span class="line"><span class="cl">- --<span class="l">source=service</span><span class="w">
</span></span></span><span class="line"><span class="cl">- --<span class="l">rfc2136-host=internal-dns.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl">- --<span class="l">rfc2136-zone=internal.k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl">- --<span class="l">annotation-filter=external-dns.alpha.kubernetes.io/internal=true</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="c"># External DNS (for public services)</span><span class="w">
</span></span></span><span class="line"><span class="cl">- --<span class="l">source=ingress</span><span class="w">
</span></span></span><span class="line"><span class="cl">- --<span class="l">rfc2136-host=external-dns.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl">- --<span class="l">rfc2136-zone=k8s.example.com</span><span class="w">
</span></span></span><span class="line"><span class="cl">- --<span class="l">annotation-filter=external-dns.alpha.kubernetes.io/internal notin (true)</span><span class="w">
</span></span></span></code></pre></div><p>The annotation filter uses label selector syntax, but <code>!=</code> is rejected (<code>&quot;!=&quot; is not a valid label selector operator</code>); <code>notin (true)</code> does the same job.</p>
<h2 id="helm-installation">Helm Installation <a class="anchor" data-pagefind-ignore href="#helm-installation" aria-label="Link to this section">#</a></h2>
<p>For production deployments, use the Helm chart. It creates the ServiceAccount, RBAC and Deployment for you; you only pass the settings.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">helm repo add external-dns https://kubernetes-sigs.github.io/external-dns/
</span></span><span class="line"><span class="cl">helm repo update
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl">helm install external-dns external-dns/external-dns <span class="se">\
</span></span></span><span class="line"><span class="cl">  --namespace external-dns <span class="se">\
</span></span></span><span class="line"><span class="cl">  --create-namespace <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set provider.name<span class="o">=</span>rfc2136 <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set extraArgs<span class="o">[</span>0<span class="o">]=</span>--rfc2136-host<span class="o">=</span>192.168.1.10 <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set extraArgs<span class="o">[</span>1<span class="o">]=</span>--rfc2136-port<span class="o">=</span><span class="m">53</span> <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set extraArgs<span class="o">[</span>2<span class="o">]=</span>--rfc2136-zone<span class="o">=</span>k8s.example.com <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set extraArgs<span class="o">[</span>3<span class="o">]=</span>--rfc2136-tsig-keyname<span class="o">=</span>external-dns-key <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set extraArgs<span class="o">[</span>4<span class="o">]=</span>--rfc2136-tsig-secret-alg<span class="o">=</span>hmac-sha256 <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set extraArgs<span class="o">[</span>5<span class="o">]=</span>--rfc2136-tsig-axfr <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set extraArgs<span class="o">[</span>6<span class="o">]=</span>--enable-legacy-annotation-prefix <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set domainFilters<span class="o">[</span>0<span class="o">]=</span>k8s.example.com <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set <span class="nv">policy</span><span class="o">=</span>sync <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set <span class="nv">txtOwnerId</span><span class="o">=</span>k8s-cluster <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set env<span class="o">[</span>0<span class="o">]</span>.name<span class="o">=</span>EXTERNAL_DNS_RFC2136_TSIG_SECRET <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set-string env<span class="o">[</span>0<span class="o">]</span>.valueFrom.secretKeyRef.name<span class="o">=</span>external-dns-tsig <span class="se">\
</span></span></span><span class="line"><span class="cl">  --set-string env<span class="o">[</span>0<span class="o">]</span>.valueFrom.secretKeyRef.key<span class="o">=</span>tsig-secret
</span></span></code></pre></div><p>What to know about the chart:</p>
<ul>
<li>The chart has no <code>rfc2136.*</code> values. Unknown keys are silently ignored, so the provider settings go in <code>extraArgs</code>.</li>
<li>The environment variable list is <code>env</code>, not <code>extraEnv</code>.</li>
<li>The chart deploys a current External-DNS release (v0.23 with chart 1.23), which reads <code>external-dns.kubernetes.io/</code> annotations. <code>--enable-legacy-annotation-prefix</code> makes it honour the <code>external-dns.alpha.kubernetes.io/</code> annotations used throughout this post as well.</li>
</ul>
<h2 id="troubleshooting">Troubleshooting <a class="anchor" data-pagefind-ignore href="#troubleshooting" aria-label="Link to this section">#</a></h2>
<p>Work from both ends: what External-DNS tried to do, and what BIND did with it.</p>
<h3 id="check-external-dns-logs">Check External-DNS Logs <a class="anchor" data-pagefind-ignore href="#check-external-dns-logs" aria-label="Link to this section">#</a></h3>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">kubectl logs -n external-dns deployment/external-dns -f
</span></span></code></pre></div><table>
	<thead>
			<tr>
					<th>Log message</th>
					<th>Meaning</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td><code>All records are already up to date</code></td>
					<td>Normal operation</td>
			</tr>
			<tr>
					<td><code>Adding RR</code> / <code>Removing RR</code></td>
					<td>Changes being made</td>
			</tr>
			<tr>
					<td><code>dns: bad authentication</code></td>
					<td>TSIG authentication issues</td>
			</tr>
			<tr>
					<td><code>REFUSED</code></td>
					<td>BIND rejecting updates</td>
			</tr>
	</tbody>
</table>
<h3 id="verify-bind-received-updates">Verify BIND Received Updates <a class="anchor" data-pagefind-ignore href="#verify-bind-received-updates" aria-label="Link to this section">#</a></h3>
<p>Enable update logging in BIND. named accepts only one <code>logging</code> block, so if your <code>named.conf</code> already has one (the RHEL default does), add the channel and categories to it instead of adding a second block:</p>
<pre tabindex="0"><code>logging {
    channel update_log {
        file &#34;/var/log/named/update.log&#34; versions 5 size 10m;
        severity debug;
        print-time yes;
    };
    category update { update_log; };
    category update-security { update_log; };
};
</code></pre><h3 id="test-connectivity">Test Connectivity <a class="anchor" data-pagefind-ignore href="#test-connectivity" aria-label="Link to this section">#</a></h3>
<p>Check that pods can reach BIND at all. The External-DNS image is distroless and has no <code>nslookup</code>, so use a throwaway pod in the same namespace:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">kubectl run -n external-dns dnstest --rm -it --image<span class="o">=</span>busybox:1.37 --restart<span class="o">=</span>Never -- <span class="se">\
</span></span></span><span class="line"><span class="cl">  nslookup -type<span class="o">=</span>SOA k8s.example.com 192.168.1.10
</span></span></code></pre></div><h3 id="manual-dns-test">Manual DNS Test <a class="anchor" data-pagefind-ignore href="#manual-dns-test" aria-label="Link to this section">#</a></h3>
<p>Send an update by hand with the same key. If this works, BIND and the key are fine and the problem is on the External-DNS side.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">nsupdate -v <span class="s">&lt;&lt; EOF
</span></span></span><span class="line"><span class="cl"><span class="s">server 192.168.1.10
</span></span></span><span class="line"><span class="cl"><span class="s">key hmac-sha256:external-dns-key &lt;secret&gt;
</span></span></span><span class="line"><span class="cl"><span class="s">zone k8s.example.com
</span></span></span><span class="line"><span class="cl"><span class="s">update add test.k8s.example.com 300 A 192.168.1.99
</span></span></span><span class="line"><span class="cl"><span class="s">send
</span></span></span><span class="line"><span class="cl"><span class="s">EOF</span>
</span></span></code></pre></div><p>Without the <code>hmac-sha256:</code> prefix, <code>nsupdate</code> assumes hmac-md5 and the update fails with <code>NOTAUTH(BADKEY)</code>. Alternatively, pass the key file: <code>nsupdate -k /etc/named/keys/external-dns.key</code>.</p>
<h3 id="common-issues">Common Issues <a class="anchor" data-pagefind-ignore href="#common-issues" aria-label="Link to this section">#</a></h3>
<table>
	<thead>
			<tr>
					<th>Symptom</th>
					<th>Check</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>Records not created</td>
					<td><code>--domain-filter</code> matches your hostnames; Service has <code>status.loadBalancer.ingress</code> populated; annotation spelling</td>
			</tr>
			<tr>
					<td>TSIG authentication failed</td>
					<td>Key name matches exactly; algorithm matches (hmac-sha256); secret is correctly encoded in the Kubernetes secret</td>
			</tr>
			<tr>
					<td>Records deleted unexpectedly</td>
					<td><code>--policy</code> setting (use <code>upsert-only</code> to prevent deletions); TXT ownership records exist; <code>--txt-owner-id</code> matches</td>
			</tr>
	</tbody>
</table>
<h2 id="security-considerations">Security Considerations <a class="anchor" data-pagefind-ignore href="#security-considerations" aria-label="Link to this section">#</a></h2>
<p>The TSIG key can change DNS records. Limit what it may change and who can reach BIND with it.</p>
<h3 id="limit-zone-access">Limit Zone Access <a class="anchor" data-pagefind-ignore href="#limit-zone-access" aria-label="Link to this section">#</a></h3>
<p>Restrict External-DNS to specific subdomains:</p>
<pre tabindex="0"><code>update-policy {
    grant external-dns-key subdomain k8s.example.com ANY;
};
</code></pre><h3 id="network-policies">Network Policies <a class="anchor" data-pagefind-ignore href="#network-policies" aria-label="Link to this section">#</a></h3>
<p>Restrict External-DNS network access. External-DNS only needs two destinations: BIND on port 53 (UDP and TCP, the latter for zone transfers) and the Kubernetes API.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">networking.k8s.io/v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">NetworkPolicy</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">namespace</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">spec</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">podSelector</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">matchLabels</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">app</span><span class="p">:</span><span class="w"> </span><span class="l">external-dns</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">policyTypes</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="l">Egress</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">egress</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c"># Allow DNS to BIND server</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">to</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">ipBlock</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">cidr</span><span class="p">:</span><span class="w"> </span><span class="m">192.168.1.10</span><span class="l">/32</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">ports</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">protocol</span><span class="p">:</span><span class="w"> </span><span class="l">UDP</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">port</span><span class="p">:</span><span class="w"> </span><span class="m">53</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">protocol</span><span class="p">:</span><span class="w"> </span><span class="l">TCP</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">port</span><span class="p">:</span><span class="w"> </span><span class="m">53</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c"># Allow API server access. The kubernetes Service (443) is translated</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c"># to the control-plane endpoints (usually :6443) before the policy is</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c"># checked, and those are host IPs that no namespaceSelector matches.</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span>- <span class="nt">to</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">ipBlock</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">            </span><span class="nt">cidr</span><span class="p">:</span><span class="w"> </span><span class="m">192.168.1.20</span><span class="l">/32 </span><span class="w"> </span><span class="c"># your control-plane node(s)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">ports</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">protocol</span><span class="p">:</span><span class="w"> </span><span class="l">TCP</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">port</span><span class="p">:</span><span class="w"> </span><span class="m">443</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span>- <span class="nt">protocol</span><span class="p">:</span><span class="w"> </span><span class="l">TCP</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span><span class="nt">port</span><span class="p">:</span><span class="w"> </span><span class="m">6443</span><span class="w">
</span></span></span></code></pre></div><p>Find the real API server addresses with <code>kubectl get endpointslices -n default -l kubernetes.io/service-name=kubernetes</code>.</p>
<h2 id="automate-it">Automate it <a class="anchor" data-pagefind-ignore href="#automate-it" aria-label="Link to this section">#</a></h2>
<p>The Ansible roles and Terraform code that build this setup are on GitHub:
<a href="https://github.com/pderuiter/blog-k8s-external-dns-bind" rel="noopener">pderuiter/blog-k8s-external-dns-bind</a>. It creates a BIND server with the TSIG key and dynamic zone, plus a single-node k3s cluster running External-DNS with the RBAC, Deployment and NetworkPolicy from this post. Run <code>terraform apply</code>, then <code>ansible-playbook site.yml</code>; <code>tests/verify.yml</code> checks that a Service&rsquo;s record appears and disappears.</p>
<h2 id="conclusion">Conclusion <a class="anchor" data-pagefind-ignore href="#conclusion" aria-label="Link to this section">#</a></h2>
<p>External-DNS with BIND gives Kubernetes automatic DNS records while BIND stays your authoritative server. RFC2136 updates with a scoped TSIG key keep it under your control.</p>
<p>The next post will cover Response Policy Zones (RPZ) for implementing DNS-based security filtering and blocking.</p>
]]></content:encoded></item></channel></rss>