Pihole not working On Some Browsers

The issue I am facing:
Hi, I'm new to the Raspberry pi as a whole. I got a pi Zero, installed pi-hole (followed a YouTube tutorial) it works great but I have noticed that it doesn't work on my mobile phone's Duck Duck Go browser. (It works on Chrome). I also have a 'social media' add list and again it works fine when accessing say, Facebook through a browser, but not through the app, which is how most people would use it, is that supposed to be like that?

Details about my system:

Pi Zero WH, I've disabled my router's DHCP and enabled it on the PiZero. - this is because I cannot find a place to Change the router's DNS to the pi.

What I have changed since installing Pi-hole:

I have restarted the browser app twice, disconnected from the WiFi and reconnected.
I'm not sure if Duck Duck go has it's own DNS Server? But I can't find a place to change it in settings.

Edit

I have checked the following browsers on the following platforms:

Chromium on Pi4 - works
Chrome on Windows10 - works
Firefox, using Duck Duck Go on windows 10 - does not work
Brave on windows10 - does not work
Microsoft Edge - does not work
Chrome on Android - works
Duck Duck Go on Android - does not work
Facebook on Android App - does not work

Debug Token: https://tricorder.pi-hole.net/0fffqvUI/

Please clarify your situation. What specifically is not working with Pi-hole and these clients?

On some browsers, you see ads, and on other browsers you do not see ads?

Some browsers are unable to connect to the internet or cannot load desired content?

1 Like

Hi

On Some browsers I still see Adds. So the pi-hole is not working for them.

I hope this makes sense :grimacing:

Check all these browsers for any private DNS settings. If you enable private DNS (or the equivalent in your browser), that browser will no longer us Pi-hole for DNS and the queries from that browser will not be filtered.

Hi, I've checked and they are all set to use the defualt dns of the service provider. (Atleast for the ones I could find the setting)

However, I've noticed something odd it seems to be inconsistent, Chrome and firefox on Win10 no longer has adds blocked, but brave does.

I'm a little lost tbh.

This is a strong indicator that this browser is using a DNS other than the DNS of Pi-hole. Note that the DNS used by the browser may be different than the DNS used by the host OS under that browser.

Edit - this link may have usable information to help you find the settings:

Help me understand this
Do I have to change each browser's DNS to use the pi-hole?

This seems like it could be annoying when I change networks between work and home?

Or am I missing a point here?

You need to change each browser to not use private DNS, if you want them to work with Pi-hole. To the best of my knowledge, this is a global setting on each browser and is not selectable by network.

1 Like

Ok I've disabled 'use Secure DNS' on all the browsers. Their behaviour did not change.
I cannot find a 'private DNS' setting on any of the browsers, and neither chrome nor Duck Duck Go has any DNS settings that I can find on mobile.

Let's take a look at the Windows client only and see what that host OS is using for DNS.

From the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of

nslookup pi.hole

nslookup flurry.com

Here you go.

That client is not using Pi-hole for DNS.

Yet pi-hole does seem to get requests from it?
Also how do I change this?

My mobile phone also sends requests to pi, but some adds are still not blocked?

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

And please provide the output of the following command from the Windows command prompt:

ipconfig /all

Ok

Here is the Token: https://tricorder.pi-hole.net/FS3OmVqI/

Here is the Windows output:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : McGillPC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : lan

Ethernet adapter Ethernet 3:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller #2
   Physical Address. . . . . . . . . : F4-4D-30-98-20-30
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 10:

   Connection-specific DNS Suffix  . : lan
   Description . . . . . . . . . . . : Remote NDIS based Internet Sharing Device #6
   Physical Address. . . . . . . . . : 00-1E-10-1F-00-00
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::a4b5:aa86:23f9:8b4a%22(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.8.215(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, 01 November 2021 18:37:51
   Lease Expires . . . . . . . . . . : Tuesday, 02 November 2021 19:01:32
   Default Gateway . . . . . . . . . : 192.168.8.1
   DHCP Server . . . . . . . . . . . : 192.168.8.2
   DHCPv6 IAID . . . . . . . . . . . : 520101392
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-03-C1-00-F4-4D-30-98-20-30
   DNS Servers . . . . . . . . . . . : fe80::1677:40ff:fe59:f7bc%22
                                       192.168.8.2
                                       1.1.1.3
                                       fe80::1677:40ff:fe59:f7bc%22
   NetBIOS over Tcpip. . . . . . . . : Enabled

Here is a problem. Only one of these DNS servers is your Pi-hole. Given multiple DNS servers, clients are free to use any of them at any time.

This client did not get those DNS assignments from the DHCP server, so this appears to be something assigned locally on the Windows client:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   * Received 300 bytes from wlan0:192.168.8.2
     Offered IP address: 192.168.8.127
     Server IP address: 192.168.8.2
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.8.2
      lease-time: 86400 ( 1d )
      renewal-time: 43200 ( 12h )
      rebinding-time: 75600 ( 21h )
      netmask: 255.255.255.0
      broadcast: 192.168.8.255
      dns-server: 192.168.8.2
      domain-name: "lan"
      router: 192.168.8.1
      --- end of options ---
    
   DHCP packets received on interface lo: 0
   DHCP packets received on interface wlan0: 1

Those settings come from the my ipv4 settings, I'll change the prefered dns to the pi-hole and leave the alternate dns blank and let you know.

Unfortunately I still get the same result...

Here is the latest

C:\Users\ME>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : McGillPC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : lan

Ethernet adapter Ethernet 3:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller #2
   Physical Address. . . . . . . . . : F4-4D-30-98-20-30
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 10:

   Connection-specific DNS Suffix  . : lan
   Description . . . . . . . . . . . : Remote NDIS based Internet Sharing Device #6
   Physical Address. . . . . . . . . : 00-1E-10-1F-00-00
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::a4b5:aa86:23f9:8b4a%22(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.8.215(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, 01 November 2021 19:41:52
   Lease Expires . . . . . . . . . . : Tuesday, 02 November 2021 19:41:52
   Default Gateway . . . . . . . . . : 192.168.8.1
   DHCP Server . . . . . . . . . . . : 192.168.8.2
   DHCPv6 IAID . . . . . . . . . . . : 520101392
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-03-C1-00-F4-4D-30-98-20-30
   DNS Servers . . . . . . . . . . . : fe80::1677:40ff:fe59:f7bc%22
                                       192.168.8.2
                                       fe80::1677:40ff:fe59:f7bc%22
   NetBIOS over Tcpip. . . . . . . . : Enabled

I just want to say Thank you for putting in this time, it really is amazing to know there is someone with this much patience looking into my little old problem.

This is your problem, and you will need to see where this setting originates.

Aahh! You're an absolute genius!
It works now, it was under my ipv6 options! I just disabled ipv6 in my adapter setting (no need for it in my home network)

Now, how can I resolve this on my mobile devices?