Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
newtonglez opened this issue Jul 30, 2023 · 2 comments

Comments

@newtonglez
Copy link

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
Copy link

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
Copy link

NewestUser commented Oct 13, 2023

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: #42 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants