I’ve been using a Pi-hole for a while, but recently some websites have stopped loading. I’ve rebuilt the Pi-hole on a different machine with a different sd card (script install on a pi 3b with raspberry pi os). So now running a fresh install with just the single base block list.
I’m thinking it might be how the Pi-hole is used. I’ve got a tp-link modem, with primary dns set to the Pi-hole’s static up address. Devices are also manually pointing to local ip on that network. Upstream dns is ip4 to open dns
Expected Behaviour:
Websites load.
Actual Behaviour:
Some websites load (arstechnica.com as an example). Others do not (DuckDuckGo.com)
I’ve added some more blocklists to check that was working. I’ve also changed the modem so it is not using the Pi-hole as the dns server, which means I could upload the debug file.
I note that your Pi-hole is configured for your Pi-hole host machine's eth0 interface, but that is connected via wlan0 instead:
*** [ DIAGNOSING ]: Network interfaces and addresses
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
inet 192.168.1.2/24 brd 192.168.1.255 scope global noprefixroute wlan0
valid_lft forever preferred_lft forever
inet6 240<redacted>d4/64 scope global mngtmpaddr noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::<redacted>18/64 scope link
valid_lft forever preferred_lft forever
That should not be an issue with your current Pi-hole Interface Settings (Allow only local requests), but still, you may want to run pihole -r with Reconfigure to adjust for wlan0 accordingly.
Your debug log also shows that you have defined some clients, all of them assigned to the default group, and you have only exactly one group, the default group.
This is a valid configuration, but you should note that Pi-hole would treat any client to the default group anyway, i.e. there would be no need to add clients if you intend to use the default group only.
As for your issue:
Pi-hole is not loading any websites - your client's browser does that.
Pi-hole can only be involved if it would not provide an IP address for a domain that a browser requests resolution of.
That could happen if your Pi-hole would block that domain, or if one of Pi-hole's upstreams would have issues resolving it (e.g. because it would be inaccessible, unresponsive or blocking domains itself).
Apologies I misspoke when saying the Pi-hole wasn’t loading. I understand the distinction. Thanks for the recommendations on working out where the ads are coming from.
I did as suggested and reconfigured to wlan0. I thought I had done that on setup, but apparently not. Regardless it appears to have fixed the issues (DuckDuckGo at least). Thank you!