Closed unclamped closed 1 year ago
Just noticed, unbound won't restart for whatever reason, it's just stuck
🤔
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.
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
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
That might or might not have something to do, I don't know /shrug
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 runningsudo grep -v '#\|^$' -R /etc/unbound/unbound.conf*
from an SSH session, I get the following output:unbound-checkconf
returns no errors, just in case