Browsers do not resolve any addresses after migrating to pihole

[Mark_Stevenson]

I have a new pihole installation. But I'm unable to use it as when I enable it, no browsers on my win10 PC (Chrome, Edge, Gener8) can connect to any websites. However command line nslookup's on the same PC are working and show pi.hole as the DNS servers. Other devices such as ipad and phone seem to work fine.

My router is a BT smart hub 2 and I have DHCP and IPv6 address allocation disabled, forcing it to go to the pihole. On the PC I have tried ipconfig /release and /renew and I've rebooted it.

Debug Token:

https://tricorder.pi-hole.net/IuKD5OUI/

[yubiuser]

@Mark_Stevenson

DHCP and IPv6 address allocation disabled,

It seems, this was not successful

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the wlan0 interface:
    192.168.1.116/24

[✓] IPv6 address(es) bound to the wlan0 interface:
    fd00:fxxxxx
    2a00:xxxxxxxxxxxxx
    fe80::xxxx4

   * Received 350 bytes from wlan0:192.168.1.254
     Offered IP address: 192.168.1.116
     Server IP address: 192.168.1.254
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.1.254
      lease-time: 86400 ( 1d )
      renewal-time: 43200 ( 12h )
      rebinding-time: 75600 ( 21h )
      netmask: 255.255.255.0
      broadcast: 192.168.1.255
      domain-name: "home"
      dns-server: 192.168.1.254
      router: 192.168.1.254
      wpad-server: "
"
         --- end of options ---
    
   * Received 300 bytes from wlan0:192.168.1.116
     Offered IP address: 192.168.1.113
     Server IP address: 192.168.1.116
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.1.116
      lease-time: 86400 ( 1d )
      renewal-time: 43200 ( 12h )
      rebinding-time: 75600 ( 21h )
      netmask: 255.255.255.0
      broadcast: 192.168.1.255
      dns-server: 192.168.1.116
      domain-name: "lan"
      router: 192.168.1.1
      --- end of options ---

There is a second DHCP server on 192.168.1.254 advertising itself as DNS server

Please run from your windows PC

nslookup pi.hole
nslookup pi.hole 192.168.1.116

[Mark_Stevenson]

I have managed to resolve this now. For any other BT users with SmartHub 2 here is what I did.

1. On the router in advanced settings disable ULA and set IPv6 address allocation to OFF.
2. At this point I found the router would still advertise itself as a DNS server until I had switched it off and on again.
3. The next problem is the default gateway. By default pihole sets the gateway to 192.168.1.1. But the BT router by default sets it's IP address to 192.168.1.254. not sure if this can be changed on the router, so I changed it at the pihole end.