Pihole not working On Some Browsers

[jfb]

@McGill

DNS Servers . . . . . . . . . . . : fe80::1677:40ff:fe59:f7bc%22
192.168.8.2
1.1.1.3
fe80::1677:40ff:fe59:f7bc%22

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.

Why should Pi-hole be my only DNS server?

Reduced Ad Blocking Capability The main reason you should Pi-hole as your only DNS server is that you will see increased performance in the blocking of ads. If you have two DNS servers (Pi-hole and something else), your network clients may not always query Pi-hole for name resolution. If a query happens to be answered from a non-Pi-hole DNS server, your block lists will not apply (since that DNS server doesn't know about them). All Queries Need To Go Through Pi-hole First Since other DNS serv…

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