container unbound unhealthy

uniquegch

I am not sure for how long, but the container unbound (ver. 1.18) is always unhealthy. looking at the ports (netstat -tulpn) there is no listening on port 53, which is open in the UFW.

at this point all the containers are up and running and healthy.

DocFraggle

uniquegch at this point all the containers are up and running and healthy

So… is unbound healthy or not? I’m confused 🤔

esackbauer

Check the watchdog logs, why it is unhealthy.
Of course its not listening on port 53 von the host level, because its not an authorative name server (its just a resolver). It uses port 53 TCP/UDP outbound. And is listening only on the mailcow internal docker network.

uniquegch

well based on watchguard (in the mailcow admin website - Logs) it is 5 of 5 aka fully healthy.
Should Iook at /var/logs?

accolon

As I described here, all the health check does is running nslookup mailcow.email 127.0.0.1 inside the unbound container, i.e. asking unbound to resolve mailcow.email.

If this fails, it’s probably a DNS problem. You can try to run the command above manually inside the container to see if and why it fails.

uniquegch

b1pum

I have the same problem. Reinstalled VM with Debian.
Some Docker containers don’t start because unbound is a requirement and unbound is started unhealthy.
The ./healthcheck.sh in the container says:
Maybe check your outbound firewall, as it needs to resolve DNS over TCP AND UDP!

nslookup mailcow.email 127.0.0.1 
;; connection timed out; no servers could be reached

./docker-entrypoint.sh 
Setting console permissions...
Receiving anchor key...
Receiving root hints...
############################################################# 100.0%
setup in directory /etc/unbound
removing artifacts
Setup success. Certificates created. Enable in unbound.conf file to use