Please follow the below template, it will help us to help you!
Expected Behaviour:
When I manually configure my Macbook's (11.3.1) DNS to use my Pi-hole's (standard Pi 400) IP, websites/dig load (with ads blocked, though loading would be a prerequisite!).
; <<>> DiG 9.10.6 <<>> www.cnn.com
;; global options: +cmd
;; connection timed out; no servers could be reached
Notably, the query shows up in my Pi-hole's logs as OK, for the relevant entries. But that information, for whatever reason, doesn't make its way back to my laptop.
For context, I am using the manual configuration per-device option, because I have a router (Spectrum 6), which doesn't seem to support good configuration. I'm attempting to bypass that, and if it means manually setting up DNS per-device, I'd be fine with it. Unfortunately, even that doesn't seem to work.
Things I have tried:
changing between upstream DNS providers
toggling IPv6 boxes on settings/DNS page (currently set the way the setup script left them)
messing with DHCP setting
looking for this setting but I don't think it's available to me, and I'm not sure if it's relevant when setting up DNS the way I am.
Not intentionally! I have a very vanilla set up. Could it possibly be something proprietary from my ISP (Spectrum)? FWIW, everything works fine without the Pi-hole in the mix. Out of curiosity, is there anything in particular in those results I shared that's leading you to think that? Also, to clarify, do you mean a firewall (for instance) on my laptop, Pi device, or router?
Firewall would be on the Mac itself. Are you running any Security software, like an antivirus package (AVG, Norton, McAfee, for example) on this device? Some of these may have a firewall or DNS component that's getting in the way. Just a thought.
Gotcha. Yeah, not intentionally. One more data point here: I also tried setting custom DNS up on my phone, and got the same result: loading any page hangs then fails. To me, I guess this suggests a Pi or router setup issue, but it could be a coincidence.
Apologies if this is a silly question, but is that good or bad? Looked at the link you sent and I'm not sure what to make of the firewall section--am I supposed to have set that up before running the install script? I guess I thought the script was taking care of that, but that could've been mistaken.
No firewall rules would just seem to indicate that there is no firewall running on your Pi (assuming that's where you ran the firewall commands from). So that would mean it's not a firewall on the Pi blocking your access to Pihole. I'm sure more suggestions will be forthcoming.
Apologies accepted
Thats not an easy question to answer.
Some say you need to run a firewall on every system.
Some say if you know what ports are listening, you wont need one.
Before or after doesnt matter (before is preferred).
But as soon as you want to make use of the Pi-hole service, those required ports need to be allowed on any firewalls that sit between your clients and Pi-hole.
Pi-hole is not gona touch your firewall as there are many firewall tools available and many ways to setup a firewall.
Huh, but if I've got no firewall, which the earlier results showed, that means it's not a necessary step, right? Putting security aside for the minute, in the interest of just getting things working. So my failing to do that wouldn't be the issue at hand?
For context, I'm setting all this up on a brand new Pi.
