I'll introduce you to the concept of WAF, Wife Acceptance Factor.
Basically, all smart IoT devices MUST default back to dumb behaviour in an expected manner. All MITM systems must either fail gracefully, fall back simply, or be robust enough to not fall over.
My NAS is currently sitting apart while I turn my wife's old PC into our new media/game/whatever server, it's been 3 weeks of different random shit not working/being forgotten (whoops, I tossed all my old sata cables! Oops, forgot that the PSU is shit and needs replacement! Oops, the dog PISSED ON JT AND RUINED THE MOTHERBOARD)
Wife is clearly annoyed that the automatic piracy machine isn't working and has threatened to resubscribe to streaming services if I don't fix it soon lol
(Just gonna upgrade my gaming PC and use MY old parts to cover the busted mobo I guess)
Get yourself a partner(s) who know a thing or two about tech and can at least perform basic troubleshooting and report to you.
Huge, thick cock but tiny brain and reeeeeeeeee? Pass. Small cock but can tell me when my homelab goes down, what services are actually affected, and suggest a solution that is plausible and is for up-to-date versions of X? Call in pizza and ice cream and clear your schedule, it's sexy time. And they knew a temporary solution for the outage so they aren't impacted while I was busy/away? Marry me.
There's a lot of other factors but that defo plays a factor. Learn tech, get blowjobs. It's that simple.
First of all, my parents have a Raspberry Pi V1.0 (the still holeless one) that has been piholing since day one. That's like a decade.
I keept it there, caseless and dangling from the lan cable, for sentimental reasons, I've grown fond of it.
Second of all, there is a secondary dns on Proxmox should the Pi need a rest.
Edit:
Forgot the third of all - that Raspberry doesn't even have a heatsink, much less a fan.
It's called a secondary DNS server. Like, literally the reason it exists. I guess it's still on the line towards knowing what TF you're doing.
Every DHCP server offers at least 2 dns server options.
This is a mistake you only make once, which is why I now have a dedicated dmz network for work equipment that doesn't use the pihole for DNS resolution.
Full arr stack makes life much easier. Only time I got that look was when it pulls a .rar that didn't automatically extract. Wrote a script that transmission runs on completion and they extract when finished now.
Can confirm. Everything is broken. I wish I could say I was typing this on the laptop I built by duct taping a battery, a screen and a pi into a laptop but that doesn't work either because I have to mod up a laptop keyboard fpga hackfuck first 🤷
Its a rookie mistake to implement a highly desirable, but low WAF (wife acceptance factor) solution to some shared resource.
The linked picture should have had a separate SSID that doesn't route through Pihole, so if the raspberry pie dies, wife know to simply change the SSID she connects to.