[question] Local Bind9 Server conflicts with docker0 interface
Summary
Docker0 interface is being resolved and the DNS Clients cannot deal with the address.
BIND version used
BIND 9.18.1-1ubuntu1-Ubuntu (Stable Release)
Steps to reproduce
On a fresh Ubuntu 22.04 Server install and set Bind9 up. After that install docker.
What is the current bug behavior?
Nslookup from a client-PC 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
What is the expected correct behavior?
I should have the following answer:
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
Relevant configuration files
Interfaces from the ns1 server:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether f0:1f:af:5d:be:90 brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 192.168.0.10/24 brd 192.168.0.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 2a02:8084:601b:b80:f21f:afff:fe5d:be90/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 920763sec preferred_lft 317904sec
inet6 fe80::f21f:afff:fe5d:be90/64 scope link
valid_lft forever preferred_lft forever
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether e0:9d:31:07:f0:e8 brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:3a:db:3b:55 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
Possible fixes
I should have a way to take docker0 interface out from name resolution.