Expected Behaviour:
Ads should be blocked on all devices; nslookup pi.hole should work.
Actual Behaviour:
Desktop PC: 192.168.1.100 (static)
Plusnet Hub One: IP is 192.168.1.254, DHCP disabled
Pihole: DHCP Enabled - 192.168.1.64-192.168.1.251; Router (gateway) IP address: 192.168.1.254
Windows 10 desktop ethernet PC listed in 'Currently active DHCP leases' (renewed/reflushed several times)
Mobile listed in Network overview as going via PiHole
Desktop PC 'Device does not use Pi-hole'
Firewall disabled
nslookup pi.hole:
*** dns.google can't find pi.hole: Non-existent domain
Server: dns.google
ipconfig/all:
Address: 8.8.8.8
DHCP Server . . . . . . . . . . . : 192.168.1.93
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
Ethernet Status (as above basically):
IPv4 Default Gateway: 192.168.1.254
IPv4 DHCP Server: 192.168.1.93
IPv4 DNS Servers: 8.8.8.8, 8.8.4.4
Rebooted PC, router and Pi several times
IPv6 avoided for now
Ads appear in Edge & Chrome
Whilst rebooting the Pi, I can happily access sites on the net.
Pi UI is working nicely
Android device seems to go via PiHole
Debug Token:
https://tricorder.pi-hole.net/voKAUvWI/
Update:
(I'll leave this here if it helps) - Windows was set to only ever use 8.8.8.8 (for IPv4) so I changed this to automatic which has caused it to start using the pi-hole (the Web UI confirms this).
nslookup pi.hole gives this now:
Server: pi.hole
Address: 192.168.1.93
Name: pi.hole.lan
I'm still seeing some adds (I tried ipconfig/dnsflush) but I reckon a reboot of everything later might work...