Bind9 Server conflicts with docker0 interface

[Nick Tait]

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20220506/1bc63d63/attachment.htm>