Pihole unbound and apt update resolving issues

Expected Behaviour:

resolve through unbound
and/or
if unbound is disabled and dns is google and quad9. i still should be about to use apt update

Actual Behaviour:

i can ping, nslookup and dig raspbian.raspberrypi.org successfully, but apt will not work with or without unbound and settings restarted.

so the main problem is i can not resolve certain websites. ie xboxlive. I can see it resolve in the logs but still does not reach the device. Unbound has been working for weeks and then magicly doesnt. After disabling unbound and setting nameservers to google and quad9, restarted dhcpd, pihole-ftl still can not resolve specific services via other devices. yet i can go to website on my laptop.
I have research forums and have tried everyone's advice and no dice.

Debug Token:

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

0% [Connecting to raspbian.raspberrypi.org (2a00:1098:0:80:1000:75:0:3)] [Connecting to archive.raspberrypi.org (2a00:1098:88:26::1:1)]

is the result of apt update after it cycles through the ipv4 addresses, and i have also tried to force ipv4 during updates and still does not work.

Err:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
  Cannot initiate the connection to raspbian.raspberrypi.org:80 (2a00:1098:0:80:1000:75:0:3). - connect (101: Network is unreachable) Could not connect to raspbian.raspberrypi.org:80 (93.93.128.193), connection timed out
Err:2 http://archive.raspberrypi.org/debian buster InRelease
  Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:88:26::2:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:88:26::1:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:88:26::1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:80:56::3:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:84:1e0::2). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:82:47::2:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:80:56::1:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:84:1e0::1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:84:1e0::3). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:82:47::1:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:82:47::1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:80:56::2:1). - connect (101: Network is unreachable) 
Could not connect to archive.raspberrypi.org:80 (93.93.135.118), connection timed out 
Could not connect to archive.raspberrypi.org:80 (93.93.130.212), connection timed out 
Could not connect to archive.raspberrypi.org:80 (176.126.240.84), connection timed out 
Could not connect to archive.raspberrypi.org:80 (46.235.227.39), connection timed out 
Could not connect to archive.raspberrypi.org:80 (93.93.135.141), connection timed out 
Could not connect to archive.raspberrypi.org:80 (46.235.231.145), connection timed out 
Could not connect to archive.raspberrypi.org:80 (176.126.240.167), connection timed out 
Could not connect to archive.raspberrypi.org:80 (46.235.230.122), connection timed out 
Could not connect to archive.raspberrypi.org:80 (46.235.231.151), connection timed out 
Could not connect to archive.raspberrypi.org:80 (176.126.240.86), connection timed out 
Could not connect to archive.raspberrypi.org:80 (93.93.135.117), connection timed out 
Could not connect to archive.raspberrypi.org:80 (46.235.231.111), connection timed out
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/buster/InRelease  
Cannot initiate the connection to raspbian.raspberrypi.org:80 (2a00:1098:0:80:1000:75:0:3). - connect (101: Network is unreachable) 
Could not connect to raspbian.raspberrypi.org:80 (93.93.128.193), connection timed out
W: Failed to fetch http://archive.raspberrypi.org/debian/dists/buster/InRelease  
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:88:26::2:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:88:26::1:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:88:26::1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:80:56::3:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:84:1e0::2). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:82:47::2:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:80:56::1:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:84:1e0::1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:84:1e0::3). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:82:47::1:1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:82:47::1). - connect (101: Network is unreachable) 
Cannot initiate the connection to archive.raspberrypi.org:80 (2a00:1098:80:56::2:1). - connect (101: Network is unreachable) 
Could not connect to archive.raspberrypi.org:80 (93.93.135.118), connection timed out 
Could not connect to archive.raspberrypi.org:80 (93.93.130.212), connection timed out 
Could not connect to archive.raspberrypi.org:80 (176.126.240.84), connection timed out 
Could not connect to archive.raspberrypi.org:80 (46.235.227.39), connection timed out 
Could not connect to archive.raspberrypi.org:80 (93.93.135.141), connection timed out 
Could not connect to archive.raspberrypi.org:80 (46.235.231.145), connection timed out 
Could not connect to archive.raspberrypi.org:80 (176.126.240.167), connection timed out 
Could not connect to archive.raspberrypi.org:80 (46.235.230.122), connection timed out
 Could not connect to archive.raspberrypi.org:80 (46.235.231.151), connection timed out 
Could not connect to archive.raspberrypi.org:80 (176.126.240.86), connection timed out 
Could not connect to archive.raspberrypi.org:80 (93.93.135.117), connection timed out 
Could not connect to archive.raspberrypi.org:80 (46.235.231.111), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.

These are OS level connectivity issues, and not a failure of Pi-hole.

The domains are being resolved (which is what Pi-hole does), but the device cannot complete the connection. That indicates a connectivity problem at the OS level.

dont know what it was but just reformatted and got a fresh pi with pihole installed and everything works but prime video and xbox live. even with pihole disabled. Services look to up as well. im baffled.

new debug

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

This points to an issue outside of Pi-hole. If Pi-hole is disabled, it is blocking nothing. If the content won't load when nothing is being blocked, the problem lies elsewhere.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.