Car-dependent infrastructure is antithetical to wheelchair and blind accessibility anyway. They’re much better off in a safer environment free of multi-ton death machines driving 45mph.

Aha, thank you. Shouldn’t have riffed from memory on that one, I suppose!

But very much agreed: the Zero series has plenty of beef for a DNS server. Maybe when the 3 comes out I’ll add one as a backup for my 4 server.

Funny enough, the Pi Zero uses the CPU from the 3 and the Zero 2 uses the CPU from the 3+, so they’re both more powerful than a 2 anyway :)

Just be sure that the second server in the list is also a black hole. If you don’t, all black holed requests will fallback to the second DNS… which, if it doesn’t also black hole them, will wind up serving you ads and defeating the point!

Personally I find a single Pi is just fine for DNS. It only takes like 10 seconds to reboot. Less, if you use M.2 storage via a HAT or boot from USB! That’s pretty fine downtime. But if you’re afraid you’ll knock over the network and get yelled at by your family or housemates, best to use a backup :)

GrapheneOS kills support when Google kills security updates, I believe. Source: my Pixel 4a came out in 2020, and Graphene already strongly recommends against using it and dropped updates entirely a few months ago.

Lineage and Pixel Experience ROMs are better at long-term support. But any custom ROM on older non-officially-supported phones is vulnerable to firmware exploits, since those fixes are typically distributed as binaries by the hardware manufacturer (Qualcomm etc). So I understand why Graphene drops support so quick, since they want all Graphene users to benefit from strong security practices.