External Pi-hole not working
Have FWG with 3 network segments. 192.168.2.1 (home - a couple wired clients and many wireless clients on Eeros in Bridge mode )
192.168.3.1 (work - a couple wired clients and many wireless clients on a TPLink A8 in Bridge mode)
192.168.4.1 (separate network setup for my Pi-Hole per FW instructions)
I want to use Pi-hole to block ads on the “home” network. I set the DNS server in the settings for that network to be 192.168.4.2, which is the IP of the Pi and the only device on the 192.168.4.1 network, but no ad blocking happens.
Pi was erased, set up as new, assigned 192.168.4.2 IP, updated all packages, Pi-hole installed, PiVPN installed. Fresh as can be.
If I VPN to the Pi (it also runs PiVPN - Wireguard) from my iPhone over 5g, Pi-hole is working and I have ad blocking, but can’t get anything local working, even if I point individual clients to the Pi’s IP for their DNS.
Makes no sense to me. Been using this Pi with my Eero network for several years, zero issues.
Anyone got ideas?
-
I have the same setup. FWG and PiHole installed as a VM on my server. Have 3 networks setup, but I don't have an issue. In the network settings, I have 2 of the 3 networks DNS set as the PiHole and a then the PiHole will forward anything it can't resolve to my own DNS, which in turn forwards to some preset DNS if it can't resolve. I would make sure the DNS booster is turned off in the FWG for the PiHole Device, then give the FWG a good ol' reboot to see if that helps at all.
Snapshot of my config for my main LAN network, PiHole is at .2.3 and I have my DSN as secondary incase PiHole is down for some reason.
Please sign in to leave a comment.
Comments
1 comment