The issue I am facing:
Queries and the internet is working normally, but nothing is being blocked even if on the blacklist.
Details about my system:
Using unbound with pihole and pihole is running off ubuntu 20.10 fully up to date.
What I have changed since installing Pi-hole:
Adding unbound and IP configuration for the DNS to work on my network.
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
Your nslookup command from the PC shows that Pi-hole correctly blocked the requested domain.
When I go to any site with ads or manually set a site like google to the blacklist it does not work and block those domains.
Edit: It did block those requests but only 10 queries which is far from working properly.
I have found the issue. I totally forgot about this setting in chrome that I had enabled. I had it route all the traffic through 1.1.1.1 DNS and disabling it makes all the queries go through pihole.
It is fully working as it should with no problems. Sorry for the user error. Thanks for trying to diagnose the issue for me. I appreciate it.
Your debug log shows two active DHCP servers, none of them distributing Pi-hole as DNS server.
Two DHCP servers on the same link may cause issues, unless they take responsibility for distinctly separate IP address ranges.
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
* Received 278 bytes from wlo1:192.168.1.81
Offered IP address: 192.168.1.107
DHCP options:
Message type: DHCPOFFER (2)
lease-time: 86400 ( 1d )
router: 192.168.1.254
dns-server: 1.1.1.1
dns-server: 1.0.0.1
--- end of options ---
A DHCP client that would have acquired their lease via the above server at 192.168.1.81 would always by-pass Pi-hole.via 1.1.1.1 or 1.0.0.1.
* Received 346 bytes from wlo1:192.168.1.254
Offered IP address: 192.168.1.96
DHCP options:
Message type: DHCPOFFER (2)
lease-time: 300 ( 5m )
router: 192.168.1.254
dns-server: 192.168.1.254
A client acquiring a lease through your router's above DHCP server at 192.168.1.254 will use your router for DNS.
That would be a valid setup if your router would be configured to use Pi-hole as its upstream DNS server (usually, a WAN/Internet setting). If it isn't, clients will by-pass your Pi-hole via your router (and ultimately, any upstream your router is using).
It would be preferred if you would instead configure your router to distribute Pi-hole as local DNS server via DHCP (usually, a LAN/DHCP setting). This would also allow Pi-hole to attribute DNS queries to inidividual clients, which is a precondition for taking advantage of Pi-hole's group management features.
I appreciate you trying to help in that way. Here's how the internet is configured. I am using my neighbor's internet (with permission), I have a repeater broadcasting into my house, I have Pi-hole running on my laptop and using it as a server, then the internet is going to my PC. The main router is so old and locked down that you cannot set a DNS and it uses the default one set by the isp. On my extender, I can change the DNS on it but I choose not to because if I want to not use Pi-hole on a specific device and my neighbor's devices do sometimes run off my extender (whichever is closest to the device). I have it set up where they are not being touched while I have my own bubble of my setup. This is why I have the DNS' set up this way.
Despite the hassle I have to do for per-device configuration it is configured to not affect them no matter what. That's why.
I also cannot change how the extender connects to the main router too much because of how the router is I have to have things configured in a different way for me to get internet without IP issues, or else clients will not get a working IP address and even if set to static on the client it will still not work.
Here's how it is configured (this is the only way I was able to get it to work)
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
