search

MatthewVance / unbound-docker

Unbound DNS Server Docker Image
MIT License
588 stars 142 forks source link

Unhealthy: Error: error sending query: Could not send or receive, because of network error #195

Open NAmRoD21v opened 3 weeks ago

NAmRoD21v commented 3 weeks ago

I run Unbound in combination with Pi-hole, both on Docker. Both run absolutly fine. My DNS request are handled by Unbound, which is setup in Pi-hole. But one thing that is bothering me is that Unbound keeps saying it is unhealthy. The error message is: "Error: error sending query: Could not send or receive, because of network error". Although it doesn't seem to impact the Unbound container, it is something that shouldn't be shown as far as I know.

Steps to reproduce the behavior:

  1. Docker Compose Files: Pi-hole: services: pihole: container_name: pihole image: "pihole/pihole:latest" ports:
    • "53:53/tcp"
    • "53:53/udp"
    • "8080:80/tcp" environment:
    • TZ=Europe/Amsterdam
    • PIHOLEDNS=10.8.1.5#5335 volumes:
    • "/home/chuwi/docker/pihole/pihole:/etc/pihole"
    • "/home/chuwi/docker/pihole/dnsmasq:/etc/dnsmasq.d" restart: unless-stopped networks: internal-network: ipv4_address: 10.8.1.2

networks: internal-network: name: internal-network attachable: true ipam: config:

Unbound services: unbound: container_name: unbound image: "mvance/unbound:latest" ports:

networks: internal-network: name: internal-network external: true

  1. Customizations (config files) Edited the following values in unbound.conf: interface: 0.0.0.0@5335 log-local-actions: yes log-queries: yes log-replies: yes log-servfail: yes logfile: /opt/unbound/etc/unbound/unbound.log
NAmRoD21v commented 3 weeks ago

Seems to be the same issue as #175. Solved by editing the healthcheck as described there. This issue can be closed.