71–75 of 75 posts
Recently did similar except set it up on a VPS. With IP filtering so that it’s not an open resolver. (Easy in my case given static ip) Theory being that it’ll provide a bit more resilience than dual locals
Why not use a tunnel like Wireguard so that you don't need an IP filter on the rental box side? That way if your home public IP is reassigned you don't have so much work to do. Bonus encryption for DNS traffic, too.
> Having a single DNS server for your network is very stressful Common... He's talking about a home network. I also have one of my Pi set up as a DNS server (running unbound directly not PiHole though) and this thing is rock stable solid. We're talking about Linux here. I've had a Linux server reach years of uptime (kids: don't try this at home, it's not secure but it was a test of Linux's stability). Redundancy is g…
If my Docker setup goes down (and it did the other day with Docker's network bug on v25) I have no DNS available.
And having a firewall rule capturing ALL DNS traffic and redirecting it to this endpoint doesn't make it easy to quickly recover from.
So I like this idea.
All machines get the
If anyone wants a redundant system and is happy not to self-host, then I can recommend NextDNS. Works great, but not free over a certain number of requests. Can’t speak to its privacy levels though - as with anything, assume records will be supplied to authorities when required. But overall it has been great - provides network wide DNS filtering and has clients for mobile and desktop devices! With a good dashboard, r…
I switched last year from NextDNS to ControlD and highly recommend it. NextDNS continually gave me issues and the support is non-existent (not "oh, support is slow" but more "there is no support"). May be less of an issue for the HN crowd, but it got to be too much of a hassle. The product seems to be pretty stagnant as well, whereas ControlD has been improving on a regular clip. I _think_ it's more expensive than Ne…
I have two PiHole instances plugged on opposite sides of the house. Instead of the mentioned GravitySync, I just occasionally copy the backup file from the primary to the secondary pihole instance (both of which are dockerized on Raspberry Pi hardware) Works great. Rarely need to think of it. I recommend looking up the recommended whitelist and adding anything there that looks relevant to you. Last downtime was a mon…
I am also running a Pi-Hole and have wondered about what happens when/if the Pi-Hole goes down. Is there a simple way to have a failover/fallback DNS configured rather than requiring two Pi's? On failure, I'd like my DNS to just fallback to my routers default DNS - yes I'd get ad's but I think that's acceptable.