I just message you and the problem happened again ...
C:\Users\Mauricioλ ping ns1.example.lan
Pinging ns1.example.lan [172.17.0.1] with 32 bytes of data:Reply from
84.116.236.63: Destination net unreachable.Reply from 84.116.236.63:
Destination net unreachable.Reply from 84.116.236.63: Destination net
unreachable.Reply from 84.116.236.63: Destination net unreachable.
Ping statistics for 172.17.0.1: Packets: Sent = 4, Received = 4, Lost = 0
(0% loss),
C:\Users\Mauricioλ ping ns1.example.lan
Pinging ns1.example.lan [172.17.0.1] with 32 bytes of data:Reply from
84.116.236.63: Destination net unreachable.Reply from 84.116.236.63:
Destination net unreachable.Reply from 84.116.236.63: Destination net
unreachable.Reply from 84.116.236.63: Destination net unreachable.
Ping statistics for 172.17.0.1: Packets: Sent = 4, Received = 4, Lost = 0
(0% loss),
C:\Users\Mauricioλ ping ns1.example.lan
Pinging ns1.example.lan [172.17.0.1] with 32 bytes of data:Reply from
84.116.236.63: Destination net unreachable.Reply from 84.116.236.63:
Destination net unreachable.Reply from 84.116.236.63: Destination net
unreachable.Reply from 84.116.236.63: Destination net unreachable.
Ping statistics for 172.17.0.1: Packets: Sent = 4, Received = 4, Lost = 0
(0% loss),
= ( 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:
Hi folks,
Thank you for the reply.
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.Now my Bind9 clients are getting ip
192.168.0.10 favorably.
Anyway, I'd like to eliminate ip 172.17.0.1 from name resolutions.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).
It makes no sense to me. Why does Bind9 insist on adding the docker0 ip in name
resolutions.That is a mystery.
Kind regards,Mauricio
Em quinta-feira, 5 de maio de 2022 21:44:50 GMT+1, Nick Tait via bind-users
<bind-users@lists.isc.org> escreveu:
On 6/05/2022 7:51 am, Grant Taylor via bind-users wrote:
On my Bind9 server, I have the following zone-files:
forward.example.lan.db:
ns1 IN A 192.168.0.10
ns1 IN AAAA fe80::f21f:afff:fe5d:be90
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.
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.)
Can you please try updating the "1 ; Serial" line to "2 ; Serial" as shown
below:
$TTL 604800@ IN SOA ns1.example.lan. hostmaster.example.lan.
( 2 ; Serial 604800
; Refresh 86400 ; Retry
2419200 ; Expire 604800 ) ;
Negative Cache TTL
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?
Nick.
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
