chriscrowe / docker-pihole-unbound

Run Pi-Hole + Unbound on Docker
1.05k stars 274 forks source link

one-container | All unbound requests time out #185

Closed unclamped closed 1 year ago

unclamped commented 1 year ago

After installing the one-container version of this project, Pi-hole starts just fine and I can see the web panel, but all DNS queries result in a SERVFAIL. After trying to run the dig sigfail.verteiltesysteme.net @127.0.0.1 -p 5335 command, I found out that all requests to any domains are timing out, returning the following: ; <<>> DiG 9.16.33-Raspbian <<>> sigfail.verteiltesysteme.net @127.0.0.1 -p 5335 ;; global options: +cmd ;; connection timed out; no servers could be reached This also occurs if I run the same command inside the docker container. One interesting thing I noticed while trying to troubleshoot this is that if I try running sudo grep -v '#\|^$' -R /etc/unbound/unbound.conf* from an SSH session, I get the following output: image Which, if compared to when I run that same command on a shell inside the container (thanks Portainer for making that easy), is way different image That might or might not have something to do, I don't know /shrug unbound-checkconf returns no errors, just in case

unclamped commented 1 year ago

Just noticed, unbound won't restart for whatever reason, it's just stuck image

unclamped commented 1 year ago

image 🤔

unclamped commented 1 year ago

image

unclamped commented 1 year ago

Seems like this is an already existing issue, when I saw it at first I didn't think it was related, but with the screenshot I just sent it does seem to have exactly the same issue as I. https://github.com/chriscrowe/docker-pihole-unbound/issues/178 Closing in favor of the other issue.