plateee

sudo pkcon refresh
sudo pkcon update 

(Either that or)

sudo apt update && sudo apt full-upgrade

Wait, both are DHCP providers? Admittedly, I haven’t looked too deep at pihole clusters - but do they synchronize their leases? If not, there’s a chance you might have duplicate IPs which can cause some interesting network behaviors.

If your logs say both are having issues at the same time, I’d go with the second troubleshooting option - accept DHCP, but statically set DNS to the same servers your Piholes use.

If there’s an issue, it’s with the upstream DNS (reachability or their rate limiting)

DNS isn’t instantaneous - and it’s hierarchical. If your systems are configured with pihole #1 (let’s say x.x.x.21) as primary and pihole #2 (x.x.x.22) for secondary and 21 fails, there will be a time when DNS requests time out. IIRC, for Linux it’s something like 4 seconds.

I know this because I saw a really weird thing at a work lab where requests were taking 8 seconds to complete for all the internal sites, but internet sites worked immediately. Turns out two of three PDNS systems in our cluster weren’t configured properly for local lookup and systems would timeout on primary (+4 sec), timeout on secondary (+4 sec), then resolve with the tertiary server.

I’m not saying that’s what’s happening here, but if this is a recent occurrence you could start with your primary/pihole and check system logs, updates etc. Or you could take a system that has this behavior and either swap the pihole order, and/or remove the pihole from the DNS all together to see if it’s even your gear causing the issue.

man find

Or if reading isn’t their jam, head to explainshell.

I’m not going to say this shit isn’t hard - it can be challenging starting out if you don’t know where to look. But come on, at this point everyone should know ChatGPT gets shit wrong often enough not to trust it.

I once installed the OS of Linux,

But speedy, it definitely wasn’t.

The year '94, a 56k net install,

Mom please hang up the phone this instant.

Sam Altman will be watching this case with interest. Maybe he can get a new round of funding from this guy.

Yup, another vote for brother laser printers. If you’re worried about them applying updates that add DRM to toner cartridges, but you still want network printing you can do one of two things:

1. Give the printer a static IPv4 address and block egress from your router with a firewall.
2. Give it a static IPv4 address but give it a non-functional gateway (e.g. if your gateway is 10.0.0.1, make the printer’s gateway 10.0.0.254)

Heck, do both if you’re paranoid.

Either way it’s not getting updates unless you manually change things or download the firmware updates on your Linux box and apply it that way.