So I thought 'Hey, installing Pi-hole on my network would be awesome' and the nightmare has begun.
I'm just gonna start by saying that I'm a noob when it comes to Pi-hole, there might be something I missed or have done wrong, so please don't scream at me in the comments.
So my setup is as follows:
- RaspberryPi 4 with 4GB of RAM
- Raspbian buster lite
-
Client: Docker Engine - Community
Version: 19.03.11
API version: 1.40
Go version: go1.13.10
Git commit: 42e35e6
Built: Mon Jun 1 09:20:15 2020
OS/Arch: linux/arm
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.11
API version: 1.40 (minimum version 1.12)
Go version: go1.13.10
Git commit: 42e35e6
Built: Mon Jun 1 09:14:09 2020
OS/Arch: linux/arm
Experimental: false
containerd:
Version: 1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
- Interface: wlan0 (I'd like to not change it)
- Adlist: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts (Other timeout, and when they do, they halt the entire system)
- Only using ipv4
This is the final command I ran to get it running
sudo docker run -d --name pihole -p 53:53/tcp -p 53:53/udp -p 80:80 -p 443:443 -e TZ="Some/Timezone" -v "$(pwd)/etc-pihole/:/etc/pihole/" -v "$(pwd)/etc-dnsmasq.d/:/etc/dnsmasq.d/" --dns=127.0.0.1 --dns=1.1.1.1 --restart=unless-stopped --hostname pi.hole -e VIRTUAL_HOST="pi.hole" -e PROXY_LOCATION="pi.hole" -e ServerIP="192.168.0.245" --net=host -e INTERFACE="wlan0" -e IPv6=False pihole/pihole:master-armhf
I got this command after hours of troubleshooting and and it still doesn't work.
It seems to start the container ok, other than the fact that after it halts the system for couple of minutes (due to the timeouts I mentioned), but after getting to WebUI, I can delete the other adlists and it fixes that problem. The only other settings I've changed is 'Listen on all interfaces' (doesn't make a difference compared to default).
My problem is as follows:
When I point my individual devices to pi-hole as a DNS server it doesn't work (tested on Windows 10 machine and an android 10 phone; ads still load, no 'total queries' update, in 'Network' tab there's a cross under 'connected to pi-hole', next to those devices). When I point my DHCP server to pi-hole (through my router) it has the same effects (Only 127.0.0.1 is "connected to pi-hole" and sometimes other docker containers go through it). This is what I get after typing 'ipconfig /all' in cmd on Windows:
Connection-specific DNS Suffix . : local
Description . . . . . . . . . . . : Some network card
Physical Address. . . . . . . . . : Some MAC address
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.254(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : June 20, 2020 9:22:56 PM
Lease Expires . . . . . . . . . . : June 21, 2020 11:19:38 PM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.245
192.168.0.1
Am at a total loss as to what to do next. This is my debug log: https://tricorder.pi-hole.net/jux9ruygzn
P.S. There was a long system-wide halt between those commands
[✓] forumediainc.us.intellitxt.com is 0.0.0.0 via Pi-hole (192.168.0.245)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)