Pi-hole

595 readers

1 users here now

The Pi-hole® is a DNS sinkhole that protects your devices from unwanted content without installing any client-side software.

founded 2 years ago

MODERATORS

GeneralVincent@sh.itjust.works

Using Docker, blocking works on host PC, but not other devices. What am I missing? (lemmy.world)

submitted 2 months ago by ExtraMedicated@lemmy.world to c/pihole@sh.itjust.works

4 comments fedilink hide all child comments

I'm trying to figure out how to set up Pi-hole for the first time and I think I'm doing something wrong, or missing some important step(s).

I figured that using Docker would be the easiest way to get it running so I started with the sample yaml I found on the pi-hole/docker-pi-hole github page. Then I went to my router's DHCP settings and set the primary DNS to the host's IP (I'm not sure if that's the correct one to use though*).

screenshot

Eventually I was able to confirm that a site I blocked was blocked when visiting it from the host PC, but my phone and other devices on my network could still visit the site.

Then I tried copying the same IP to the secondary DNS, but then I could no longer access the internet on other devices.

I also tried disabling the router's DHCP server to use Pi-hole instead. I used the same default gateway IP I found in the router's settings, but I lost internet on the other devices with that as well.

I know very little about configuring network stuff so I'm not sure what I might've done wrong.

*I also tried using the IP address I found in the Pi-hole's system information section as the primary DNS, but then the site I blacklisted was no longer getting blocked on the host machine.

top 4 comments

sorted by: hot top controversial new old

[–] lIlIlIlIlIlIl@lemmy.world 5 points 2 months ago* (last edited 2 months ago)

Your other devices need to reference your new Pihole as their DNS provider

If you just set it, the lease in your client devices likely hasn’t expired yet

edit: re-read your post before coffee

[–] BlackEco@lemmy.blackeco.com 4 points 2 months ago (2 children)

First, are you sure your Pi-hole's DNS is exposed at port 53 and accepts traffic? Try using dig from another device to see whether it works or not

dig +short @192.168.0.175 allowed-domain.tld
dig +short @192.168.0.175 blocked-domain.tld

If Pi-hole works, you should get 0.0.0.0 as an answer for any blocked domains.

my phone and other devices on my network could still visit the site

Have you tried disconnecting and reconnecting to the network in order to make sure these devices get new DHCP leases? Once it's done, which DNS servers do they say they use? Also make sure your phone and computer's browser aren't using DNS-over-HTTPS or DNS-over-TLS (I know Firefox use Cloudflare's DNS-over-HTTPS by default in some setups)

[–] ExtraMedicated@lemmy.world 2 points 2 months ago* (last edited 2 months ago)

are you sure your Pi-hole’s DNS is exposed at port 53 and accepts traffic?

I think this is where I went wrong. dig shows that the connection times out. This may also explain why forcing clients to use that for DNS would cause them to lose internet access. Although I thought that port would be open because it's listed in the yaml file for docker-compose. Is there another step I need to open that from the host machine?

[–] ExtraMedicated@lemmy.world 2 points 2 months ago

Thanks! It's working now. I just had to open port 53 on the host (not just the docker container).