Anyone else seeing this?
sudo apt update
Hit:1 https://download.docker.com/linux/debian bookworm InRelease
Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease
Ign:3 http://deb.debian.org/debian bookworm InRelease
Ign:4 http://deb.debian.org/debian-security bookworm-security InRelease
Ign:5 http://deb.debian.org/debian bookworm-updates InRelease
Ign:3 http://deb.debian.org/debian bookworm InRelease
Ign:4 http://deb.debian.org/debian-security bookworm-security InRelease
Ign:5 http://deb.debian.org/debian bookworm-updates InRelease
Ign:3 http://deb.debian.org/debian bookworm InRelease
Ign:4 http://deb.debian.org/debian-security bookworm-security InRelease
Ign:5 http://deb.debian.org/debian bookworm-updates InRelease
Err:3 http://deb.debian.org/debian bookworm InRelease
Temporary failure resolving 'deb.debian.org'
Err:4 http://deb.debian.org/debian-security bookworm-security InRelease
Temporary failure resolving 'deb.debian.org'
Err:5 http://deb.debian.org/debian bookworm-updates InRelease
Temporary failure resolving 'deb.debian.org'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian-security/dists/bookworm-security/InRelease Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease Temporary failure resolving 'deb.debian.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Anyone know how to solve it?
Turns out it was Unbound doing shit. Thank you everyone that helped.
10 Comments
spacewave@lemmy.ml · 4 pts · 1y
Its always DNS
sabreW4K3@lazysoci.al · 2 pts · 1y
I've checked and it's still pulling DNS from my pihole, which is resolving deb.debian.org just fine.
vk6flab@lemmy.radio · 4 pts · 1y
Whenever I've seen this, the issue is an out of date image. Do a docker pull and see if it persists.
Geodad@lemm.ee · 3 pts · 1y
sabreW4K3@lazysoci.al · 3 pts · 1y
The time and date seems fine on mine
Geodad@lemm.ee · 2 pts · 1y
sabreW4K3@lazysoci.al · 1 pts · 1y
Nah, checked the resolv.conf, the nsswitch.conf and tried to check the ufw only to see it's not even available on the system. I'm baffled. Everything else on my network can resolve it just fine.
Geodad@lemm.ee · 2 pts · 1y
sabreW4K3@lazysoci.al · 1 pts · 1y
It's a super simple set-up. Virgin Media Router with DHCP turned off. Pi-Hole, doing DNS and DHCP connected via WiFi along with everything else.
Geodad@lemm.ee · 3 pts · 1y
sabreW4K3@lazysoci.al · 3 pts · 1y
I found it finally. It was only bloody Unbound shitting the bed.
retrolasered@feddit.uk · 2 pts · 1y
Oh yeah, ive had this on a public network where the port for time sync was firewalled and had to pull the time from google to fix
Geodad@lemm.ee · 1 pts · 1y
retrolasered@feddit.uk · 1 pts · 1y
Im on that network quite a lot, I dont want to do that every time im using it