Anyone know if I’m doing something wrong? I have a docker-compose file of Bind9 and PiHole.

    services:
      pihole:
        container_name: pihole
        image: pihole/pihole
        ports:
          - "5053:53/tcp"
          - "5053:53/udp"
          - "80:80/tcp"
        environment:
          TZ: 'UTC'
          WEBPASSWORD: '[redacted]'
          PIHOLE_DNS_: '1.1.1.1;1.0.0.1;2606:4700:4700::1111;2606:4700:4700::1001;'
        volumes:
          - './etc-pihole:/etc/pihole'
          - './etc-dnsmasq.d:/etc/dnsmasq.d'
        restart: unless-stopped 

      bind:
        container_name: bind9
        image: ubuntu/bind9
        ports:
          - "53:53/tcp"
          - "53:53/udp"
        environment:
          TZ: 'UTC'
        volumes:
          - './etc-bind:/etc/bind'
        restart: unless-stopped

And within the ./etc-bind folder I have the forwarder set

    options {
        forwarders {
        10.10.10.8 port 5053;
        };
    ...

I user bind for anthing on my homelab.

dig @10.10.10.8 my_thing.my_home.lan works fine.

dig @10.10.10.8 -p 5053 google.com works fine.

dig @10.10.10.8 google.com will time out.

dig @10.10.10.8 coccyxwickimp.com will time out (That one is on the pihole block list)

If I docker exec -it bind9 bash into the bind container and run dig @10.10.10.8 -p 5053 google.com it will time out.

So for some reason, the bind container can’t get any DNS requests from Pihole. The same is ALL true if I flip the roles and make Pihole the first responder and bind the next in line.

Any ideas?

So for some reason, the bind container can’t get any DNS requests from Pihole. The same is ALL true if I flip the roles and make Pihole the first responder and bind the next in line.