<html><head></head><body><div class="ydp839398ayahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false"><div dir="ltr" data-setdir="false">I just message you and the problem happened again ... </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><div><div>C:\Users\Mauricio</div><div>λ ping ns1.example.lan</div><div><br></div><div>Pinging ns1.example.lan [172.17.0.1] with 32 bytes of data:</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div><br></div><div>Ping statistics for 172.17.0.1:</div><div> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),</div><div><br></div><div>C:\Users\Mauricio</div><div>λ ping ns1.example.lan</div><div><br></div><div>Pinging ns1.example.lan [172.17.0.1] with 32 bytes of data:</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div><br></div><div>Ping statistics for 172.17.0.1:</div><div> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),</div><div><br></div><div>C:\Users\Mauricio</div><div>λ ping ns1.example.lan</div><div><br></div><div>Pinging ns1.example.lan [172.17.0.1] with 32 bytes of data:</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div>Reply from 84.116.236.63: Destination net unreachable.</div><div><br></div><div>Ping statistics for 172.17.0.1:</div><div> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),</div><div><br></div></div>= (</div></div>
</div><div id="yahoo_quoted_2353217760" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
Em sexta-feira, 6 de maio de 2022 14:38:37 GMT+1, MaurÃcio Penteado via bind-users <bind-users@lists.isc.org> escreveu:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv2142948725"><div><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;" class="yiv2142948725ydpf869acd2yahoo-style-wrap"><div></div>
<div dir="ltr">Hi folks,</div><div dir="ltr"><br clear="none"></div><div dir="ltr">Thank you for the reply.</div><div dir="ltr"><br clear="none"></div><div dir="ltr"> <div><div>I added the A-record "ns1 IN A 172.17.0.1" to my zone-file as suggested and it seems that the order fixed the issue.</div><div>Now my Bind9 clients are getting ip 192.168.0.10 favorably.</div><div><br clear="none"></div><div>Anyway, I'd like to eliminate ip 172.17.0.1 from name resolutions.</div><div>I never added this ip in my zone files and I don't have any DNS clients coming from this network (at least not at the moment).</div><div><br clear="none"></div><div>It makes no sense to me. Why does Bind9 insist on adding the docker0 ip in name resolutions.</div><div>That is a mystery.</div><div><br clear="none"></div><div>Kind regards,</div></div><div dir="ltr">Mauricio</div><br clear="none"></div>
</div><div id="yiv2142948725yahoo_quoted_2166238119" class="yiv2142948725yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
Em quinta-feira, 5 de maio de 2022 21:44:50 GMT+1, Nick Tait via bind-users <bind-users@lists.isc.org> escreveu:
</div>
<div><br clear="none"></div>
<div><br clear="none"></div>
<div><div id="yiv2142948725yqt94340" class="yiv2142948725yqt6473628170"><div id="yiv2142948725"><div>
<div class="yiv2142948725moz-cite-prefix">On 6/05/2022 7:51 am, Grant Taylor via
bind-users wrote:<br clear="none">
</div>
<blockquote type="cite">
<blockquote type="cite" style="color:#007cff;">On my Bind9
server, I have the following zone-files:
<br clear="none">
<br clear="none">
forward.example.lan.db:
<br clear="none">
ns1 IN A 192.168.0.10
<br clear="none">
ns1 IN AAAA fe80::f21f:afff:fe5d:be90
<br clear="none">
</blockquote>
<br clear="none">
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 clear="none">
</p>
<p>Can you please try updating the "1 ; Serial" line to "<font color="#ff0000"><b>2</b></font> ; Serial" as shown below:<br clear="none">
</p>
<pre><span></span></pre><div>$TTL 604800</div><div>@ IN SOA ns1.example.lan. hostmaster.example.lan. (</div><div><div id="yiv2142948725yqtfd67428" class="yiv2142948725yqt1668681989"> <font color="#ff0000"><b>2</b></font></div> ; Serial</div><div> 604800 ; Refresh</div><div> 86400 ; Retry</div><div> 2419200 ; Expire</div><div> 604800 ) ; Negative Cache TTL</div>
<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 clear="none">
</p>
<p>Nick.</p><div id="yiv2142948725yqtfd88309" class="yiv2142948725yqt1668681989"><br clear="none">
</div><div id="yiv2142948725yqtfd28869" class="yiv2142948725yqt1668681989">
</div></div></div></div><div id="yiv2142948725yqtfd05454" class="yiv2142948725yqt1668681989">-- <br clear="none">Visit <a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="https://lists.isc.org/mailman/listinfo/bind-users ">https://lists.isc.org/mailman/listinfo/bind-users </a>to unsubscribe from this list<br clear="none"><br clear="none">ISC funds the development of this software with paid support subscriptions. Contact us at <a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="https://www.isc.org/contact/ ">https://www.isc.org/contact/ </a>for more information.<br clear="none"><br clear="none"><br clear="none">bind-users mailing list<br clear="none"><a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:bind-users@lists.isc.org" target="_blank" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a><br clear="none"><a rel="nofollow noopener noreferrer" shape="rect" target="_blank" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a><br clear="none"></div></div>
</div>
</div></div></div><div class="yqt6473628170" id="yqt21999">-- <br clear="none">Visit <a shape="rect" href="https://lists.isc.org/mailman/listinfo/bind-users " target="_blank">https://lists.isc.org/mailman/listinfo/bind-users </a>to unsubscribe from this list<br clear="none"><br clear="none">ISC funds the development of this software with paid support subscriptions. Contact us at <a shape="rect" href="https://www.isc.org/contact/ " target="_blank">https://www.isc.org/contact/ </a>for more information.<br clear="none"><br clear="none"><br clear="none">bind-users mailing list<br clear="none"><a shape="rect" ymailto="mailto:bind-users@lists.isc.org" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a><br clear="none"><a shape="rect" href="https://lists.isc.org/mailman/listinfo/bind-users" target="_blank">https://lists.isc.org/mailman/listinfo/bind-users</a><br clear="none"></div></div>
</div>
</div></body></html>