Internet no longer works after upgrade

Help Community Help
1

The issue I am facing:
Upgraded from v5 to v6 and now nothing works. Websites dont load, apps wont work, etc…. I have had to remove pihole as my DNS from my router in order to use the internet.

Details about my system:
Raspberry Pi 4

What I have changed since installing Pi-hole:
Just upgraded from v5 to v6

2

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 if you run your Pi-hole as a Docker container:

docker exec -it <pihole-container-name-or-id> pihole -d

where you substitute <pihole-container-name-or-id> as required.

3

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

4

Any update?

5

Here is the debug again

https://tricorder.pi-hole.net/8yE2lG2j/

6

@Bucking_Horn any luck?

7

@Bucking_Horn Here is the latest debug

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

8

Your debug shows your Pihole to be fully operational with full IPv4 and IPv6 connectivity:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] d-clothinglingerie.t.domdex.com is NXDOMAIN on lo (127.0.0.1)
[✓] d-clothinglingerie.t.domdex.com is NXDOMAIN on eth0 (192.168.1.228)
[✓] No IPv4 address available on wlan0
[✓] d-clothinglingerie.t.domdex.com is NXDOMAIN on tailscale0 (100.122.65.63)
[✓] doubleclick.com is 142.251.40.142 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] secure3.areospolis.gr is NXDOMAIN on lo (::1)
[✓] secure3.areospolis.gr is NXDOMAIN on eth0 (2600:<redacted>55)
[✓] secure3.areospolis.gr is NXDOMAIN on eth0 (fe80::<redacted>28%eth0)
[✓] No IPv6 address available on wlan0
[✓] secure3.areospolis.gr is NXDOMAIN on tailscale0 (fd7a:<redacted>3f)
[✓] secure3.areospolis.gr is NXDOMAIN on tailscale0 (fe80::<redacted>4e%tailscale0)
[✓] doubleclick.com is 2607:f8b0:4006:81c::200e via a remote, public DNS server (2001:4860:4860::8888)

It also shows your router to distribute its own IPv4 as local DNS server via DHCP, and to advertise its own IPv6 for DNS:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 6 seconds)
   Scanning all your interfaces for DHCP servers and IPv6 routers
   
   * Received 112 bytes from fe80::<redactded>75 @ eth0
     Hop limit: 64
     Stateful address conf.: No
     Stateful other conf.: Yes
     Mobile home agent: No
     Router preference: Medium
     Neighbor discovery proxy: No
     Router lifetime: 900 s
     Reachable time: N/A
     Retransmit time: N/A
     (…)
     Recursive DNS server 1/1: 2600:<redacted>::1
     DNS server lifetime:600 sec
     (…)
   * Received 343 bytes from 192.168.1.1 @ eth0
     Offered IP address: 192.168.1.181
     DHCP options:
      Message type: DHCPOFFER (2)
      router: 192.168.1.1
      dns-server: 192.168.1.1

This could still be a valid configuration if you had configured your router to use Pi-hole as its only upstream DNS server.
Note that you would't be able to attribute DNS requests to individual client IPs in such a configuration.

9

@Bucking_Horn It’s still extremely slow. Any ideas why?

10

Did you verify and adjust your router's local DNS settings?

11

@Bucking_Horn I did. My router is set up to use the pi’s ip as its dns. I am getting a lot of caching in pi hole and recently received the error “ No valid NTP replies received, check server and network connectivity”. The web interface also takes forever to load.