Just…set up two RPIs with Pihole instead of one? Chances are your router can have a fallback DNS. Sure, you have to update the rules in both places, but honestly it’s not a big deal, and you now have redudancy.

I’m running 2 powerdns recursors and authoritative servers, and 2 piholes (long story why so many), and none of them have failed on me so far, and when I took one of them offline, I didn’t notice anything because the other took over. And if anything REALLY fails, I’ll just switch my router back to using cloudflare or Google or quad9 temporarily, and at least Internet access will be restored so people can at least browse the internet.

Pihole also has an API and a home Assistant integration, so you can create an AdBlock toggle switch for others, in case it blocks something and they need immediate access. Not ideal, but it’s a doable workaround.

This is really something that’s super easy to self host, and mitigate if something goes wrong. Especially since that commercial router is already a single point of failure for most households.

A password manager because if anything goes wrong, you’ll be completely screwed.

What you SHOULD absolutely self host though is a password manager, so you can be in control of your most sensitive data.

Regarding email, I think everyone should absolutely self host it, but it’s less and less viable in this google/Microsoft duopoly world. But ideally everyone would self host it. The reason why people advise against it really comes down to lack of real competition, and the two tech giants dictating how we violate every RFC possible.

What?

Okay, little bit of DNS basics:

if you run a commercial router at home, that runs a DNS recursor, which by default just queries your ISP DNS server, which queries another one, and so on. It’s DNS recursors all the way down. If you configure your router to use google’s DNS, now you’re just querying from Google instead your ISP.

You can also run a DNS recursor (and/or an authoritative server) separately (e.g Pihole, Bind9, PowerDNS, etc.) inside your network, and nobody else but you will have access to it. As long as you don’t expose the service directly to the wide Internet (so nobody can connect), you’re fine. DNS will work for you, but nobody else.

Also, 192.168.x.x IP addresses are private IP addresses, it’s only routeable inside your network. Nobody outside can access your stuff with those IP addresses.

I don’t know what the question was, but I’m hoping somewhere here you found some information that will help google/bing/duckduckgo around and provide you an answer. There are a lot of sources online for understanding DNS and networking, so you should look into that a bit.

I agree. I trust Bitwarden more to host it than me. I can have too many things going wrong. With that being said, I do agree with the security implications with centralized Bitwarden, but I’d rather have that risk than to screw myself over due to my own incompetence.

Someone a while ago mentioned on this sub: The best thing to host yourself is a password manager, and the worst thing to host yourself is a password manager.

Json with comments is literally perfect. Formattable, machine parsable, minimisable, easy and fairly concise. Honestly I can’t think of anything better. (Comments in json are essential IMO, without it it’s actually not that great, and I’d go with yaml instead)