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
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?
Use the same process. If they have IPv6 enabled, disable this on these clients as a start.
With IPv6, your router may be advertising its own IPv6 address as DNS server, as in your case, and thus any device may by-pass Pi-hole via IPv6.
You'd have to find a way to configure your router to advertise your Pi-hole host machine's IPv6 as DNS server instead of its own.
You'd have to consult your router's documentation sources on further details for its IPv6 configuration options.
If your router doesn't support configuring IPv6 DNS, you could consider disabling IPv6 altogether.
If your router doesn't support that either, your IPv6 capable clients will bypass Pi-hole via IPv6.
1 Like
I think this may be the root of the problem. I don't think my router deals with ipv6 at all. I can't find any dns settings whatsoever on it. I'll look at its documentation and see if I can resolve this.
Again thank you so much!
I consider it more likely it does, as there is a link-local IPv6 address (for a network adapter manufactured by Huawei) that your Windows client seems to have picked up from a router advertisement.
But if you're unlucky, then your router is not exposing the necessary options to control IPv6 DNS settings.
This is unfortunately the case, it doesn't expose any DNS Settings - my hope was that it would disable it when I disable its DHCP server. But I may have lucked out. Guess I'll get a new router. ISP routers are known to be as barebones as they come... 
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.