0

I'm busy moving a Bind9 Server into a Docker Container. The Docker Container is set up to run Debian 10 and Bind9, the setup for Bind9 is a copy of a working Bind9 Server (also on Debian 10).

The setup is as follows

Debian Docker Host (192.168.20.28)
    Debian Docker Container (10.1.2.22)
        ns1.deb10cont.lan
        ns2.deb10cont.lan
        host.deb10cont.lan
        SSH Port 222
        Apache Port 80

The Container is added to the network with a static IP

docker network connect --ip 10.1.2.22 network dnsserver

The bind9 zone is set up as

$TTL    604800
@       IN      SOA     deb10cont.lan. admin.deb10cont.lan. (
                              2         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
@       IN      NS      ns1.deb10cont.lan.
@       IN      NS      ns2.deb10cont.lan.
ns1.deb10cont.lan.      IN      A       10.1.2.22
ns2.deb10cont.lan.      IN      A       10.1.2.22
host.deb10cont.lan.     IN      A       10.1.2.22

I am also able to ping from inside the Container

ping host.deb10cont.lan
PING host.deb10cont.lan (10.1.2.22) 56(84) bytes of data.
64 bytes from hostserver (10.1.2.22): icmp_seq=1 ttl=64 time=0.019 ms

I am able to do an nslookup from another machine on the Container's domain names

nslookup host.deb10cont.lan

Server: UnKnown
Address: 192.168.20.28

Name: host.deb10cont.lan
Address: 10.1.2.22

But pings from that same machine are timing out

ping host.deb10cont.lan
Pinging host.deb10cont.lan [10.1.2.22] with 32 bytes of data:
Request timed out.

Am I missing a step? It looks like the dns is available but not resolving correctly

4

0 回答 0