<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 6/05/2022 7:51 am, Grant Taylor via
bind-users wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4f8251a9-ddc2-fdc7-0c40-eccc35386b5a@spamtrap.tnetconsulting.net">
<blockquote type="cite" style="color: #007cff;">On my Bind9
server, I have the following zone-files:
<br>
<br>
forward.example.lan.db:
<br>
ns1 IN A 192.168.0.10
<br>
ns1 IN AAAA fe80::f21f:afff:fe5d:be90
<br>
</blockquote>
<br>
I don't see the 2nd, Docker (?), address; 172.17.0.1, in the
zone. So if your client is still receiving that address in
addition to the 192.168.0.10 address, then something else is
happening outside of BIND.
</blockquote>
<p>Mauricio, was 172.17.0.1 in the zone file at any time in the
past? Because if so, I'm betting that the problem is simply that
after you removed it, you neglected to increment the SOA serial
number? (In case you weren't aware the serial number needs to be
increased every time you change the zone file.)<br>
</p>
<p>Can you please try updating the "1 ; Serial" line to "<font
color="#ff0000"><b>2</b></font> ; Serial" as shown below:<br>
</p>
<pre><span><div>$TTL 604800</div><div>@ IN SOA ns1.example.lan. hostmaster.example.lan. (</div><div> <font color="#ff0000"><b>2</b></font> ; Serial</div><div> 604800 ; Refresh</div><div> 86400 ; Retry</div><div> 2419200 ; Expire</div><div> 604800 ) ; Negative Cache TTL</div></span></pre>
<p>Once you've done that, run "sudo rndc reload" on your the primary
DNS server for the zone (or alternatively restart BIND), and see
if that makes a difference?<br>
</p>
<p>Nick.<br>
</p>
</body>
</html>