Bind9 Server conflicts with docker0 interface

[Reindl Harald]

Am 05.05.22 um 16:05 schrieb Maurà cio Penteado via bind-users:
>
>
>       What is the current behavior?
>
> Nslookup from a DNS Client workstation  should not get docker0 ip 
> addrees of the Bind9 Server PC.
> |nslookup ns1.example.lan Server: UnKnown Address: 
> fe80::f21f:afff:fe5d:be90 Name: ns1.example.lan Addresses: 
> 2a02:8084:601b:b80:f21f:afff:fe5d:be90 192.168.0.10 172.17.0.1|
> Relevant configuration files
>
> Interfaces from the ns1 server:
>
the relevant config file would have been the zone-file

> ||
>
> Please, can you help?
> How can I stop Bind to resolve docker0 ip address?

by not add multiple A-records for the same name to the zone-file
BIND don't know about docker on it's own

and please avoid HTML formatted mails, it makes responding with inline 
quotes more difficult as it should be


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20220505/bf9a67d9/attachment-0001.htm>