Clients don't use Pi-hole

[Blake]

@yubiuser

Your router still advertises its own IP as DNS server via DHCP. Try setting Pi-hole as DNS server via DHCP. Afterwards dis/reconnect your clients once from the network to pickup the new information.

I have a similar issue and I have set my dns server on the rooter to the pihole at 223 however my server IP is still 1. I have similar log to the one posted here . Is there a way to resolve this or set the Pihole to handle DHCP ?

[yubiuser]

I moved your post to a new topic.

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

[Blake]

Hello everyone ,

I am quite new to these forums , I have been trying to resolve my problem for the past 5 days, and after multiple installations and searching through forums online I finally gave up and decided to ask for help .
I have this installation on a raspberry pi 3 , I have my Linksys smart wifi router pointing at pihole as its dns server, all the requests seems to be going through pihole but its not actually working to block these ads on network devices, Pihole is only working on the raspberry pi its installed on .
Its also been giving me rate limit errors which I resolved by changing a confi file, and setting the rate limit to 0/0, Also some errors to do with packet sizes.

Expected Behaviour:

To block ads , network wide. Set as the dns server on the dhcp settings of my Linksys smart wifi router.

Actual Behaviour:

It is only blocking ads on the raspberry pi device but none other.

Debug Token:

tricorder.pi-hole.net/D4G5iThH

[yubiuser]

Your debug log shows no errors, and is working fine.

   [2022-01-02 22:50:16.071 16268M] Imported 114944 queries from the long-term database
   [2022-01-02 22:50:16.072 16268M]  -> Total DNS queries: 114944
   [2022-01-02 22:50:16.073 16268M]  -> Cached DNS queries: 3727
   [2022-01-02 22:50:16.073 16268M]  -> Forwarded DNS queries: 106040
   [2022-01-02 22:50:16.073 16268M]  -> Blocked DNS queries: 4190
   [2022-01-02 22:50:16.073 16268M]  -> Unknown DNS queries: 0
   [2022-01-02 22:50:16.073 16268M]  -> Unique domains: 1624
   [2022-01-02 22:50:16.073 16268M]  -> Unique clients: 3
   [2022-01-02 22:50:16.073 16268M]  -> Known forward destinations: 11

However, you distribute your router's IP as DNS server via DHCP. You could exchange this IP for Pi-hole's IP to announce it as DNS server via DHCP. This would have the advantage that you can see individual clients on your dashboard and can use the group management feature.

[✓] IPv4 address(es) bound to the wlan0 interface:
    192.168.1.223/24

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   * Received 332 bytes from wlan0:192.168.1.1
     Offered IP address: 192.168.1.223
     Server IP address: 192.168.1.1
     Relay-agent IP address: N/A
     BOOTP server: ecosystem.home.cisco.com
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.1.1
      lease-time: 86400 ( 1d )
      renewal-time: 43200 ( 12h )
      rebinding-time: 75600 ( 21h )
      netmask: 255.255.255.0
      broadcast: 192.168.1.255
      domain-name: "cust.communityfibre.co.uk"
      hostname: "raspberrypi"
      dns-server: 192.168.1.1
      router: 192.168.1.1
      --- end of options ---

Additionally, you use IPv6. That's OK, however your clients got GUA addresses (2a02:....) which might change frequently due to changed prefixes. You should see if you could use stable ULA addresses instead:

Use IPv6 ULA addresses for Pi-hole

Many users have reported that frequently changing IPv6 addresses cause page load to be slow or even prevent from working at all. The issues can be fixed by updating the IPv6 address in /etc/pihole/setupVars.conf followed by a run of pihole -g. However, this solution turns out to be very inconvenient since it might be necessary to change the IPv6 address on a regular basis (maybe even multiple times a day). An alternative approach we are currently looking into is the usage of ULA addresses which…

[Blake]

Thank you for the reply, After looking at your reply, I realised that I could add more lists to gravity and help me block more ads and other malicious traffic that I was after. Very useful insight, I have been trying to advertise Pihole's address as the DNS through DHCP to use the group management but for some reason It has not been successful.

I will look further Into the IPV6 issue and try resolve that, Thank you !