search

chriscrowe / docker-pihole-unbound

Run Pi-Hole + Unbound on Docker
1.04k stars 270 forks source link

The image build cant not resolve without explicity make request to 127.0.0.1:53 #215

Open newtonglez opened 12 months ago

newtonglez commented 12 months ago

hi, i run bash into the image:

docker exec -it pihole bash

And if i try a simple ping pi-hole.net doesn't resolve

i try with dig pi-hole.net @127.0.0.1

And works ok.

the content of file /etc/resolv.conf is nameserver 127.0.0.11 options ndots:0

i guess this is the cause of fail, this content is correct?

NewestUser commented 9 months ago

same issue here

I am running a fresh install using portainer. pi-hole web UI opens OK and I am able to see queries on the dashboard however the logs of the container state DNS resolution is unavailable:

Starting unbound
  [✗] DNS resolution is currently unavailable
NewestUser commented 9 months ago

same issue here

I am running a fresh install using portainer. pi-hole web UI opens OK and I am able to see queries on the dashboard however the logs of the container state DNS resolution is unavailable:

Starting unbound
  [✗] DNS resolution is currently unavailable

I was able to fix this by adding a dns property in docker-compose


services:
  pihole:
    ...
    dns:
      - "127.0.0.1"

Thanks to this guy: https://github.com/chriscrowe/docker-pihole-unbound/issues/42#issuecomment-904969367