I'm convinced an utter lack of empathy is the reason why there's a constant 40% support of Trump.
How many times do you read stories about some Republican politician or right winger suddenly be not as horrid toward "the gays" because their kid came out? (Admittedly, that seems to happen a whole lot less now)
These people just can't put themselves in the shoes of anyone who isn't exactly like them.
sudo pkcon refresh
sudo pkcon update
(Either that or)
sudo apt update && sudo apt full-upgrade
Can we double click on that for a second?
More often than not, my keys are in my hoodie pocket... under the jacket.
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.
OMG, if the government shutdown could end snaps for app installs, I would be so happy.
AppImage or die.
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.
The trick is to use your PTO all at once and be out for a week or so - everything falls over and it reminds your boss how you're the only thing keeping it all together.
When he said that, I instantly felt jealous.