21–30 of 75 posts
A simpler solution: Deploy one Pi-Hole instance and then set clients to use Pi-Hole as the primary resolver and your ISP/router as the secondary. In the rare circumstance that the Pi-Hole device is down, you fallback and get the "normal" ISP DNS service.
I recently set up a Pi-Hole for the first time, but I spun it down pretty quickly. On desktop / mobile I already have client-side ad-blocking, and it's not like the Pi-Hole can block embedded ads in adware apps like YouTube on iOS, so I just couldn't really justify keeping it powered. I suppose if you have a house full of Samsung / Huawei / etc. IoTs that you really need to keep connected to the Internet for whatever…
I set up my Pi-Hole on a Raspberry Pi Zero W. I have some brief notes here on my setup: https://www.thelis.org/blog/pi-hole. It works well.
I recently set up a Pi-Hole for the first time, but I spun it down pretty quickly. On desktop / mobile I already have client-side ad-blocking, and it's not like the Pi-Hole can block embedded ads in adware apps like YouTube on iOS, so I just couldn't really justify keeping it powered. I suppose if you have a house full of Samsung / Huawei / etc. IoTs that you really need to keep connected to the Internet for whatever…
Thanks for the info. I thought this was possible and it was the sole reason why I considered setting one up. Now I procrastinated on that project long enough to learn I can cancel it.
A simpler solution: Deploy one Pi-Hole instance and then set clients to use Pi-Hole as the primary resolver and your ISP/router as the secondary. In the rare circumstance that the Pi-Hole device is down, you fallback and get the "normal" ISP DNS service.
This line/'service'; Really?! Why? Finally, since 32GB is a relatively small disk, I installed a daily cron job to clean the apt cache[0]: Which is a Debian package to run `apt-get clean` that the author of the blog created. Here you go, no package required: # printf 'apt-get clean\n\n' > /etc/cron.daily/daily-apt-clean && chmod +x /etc/cron.daily/daily-apt-clean` [0] - https://github.com/cdzombak/apt-daily-clean
A simpler solution: Deploy one Pi-Hole instance and then set clients to use Pi-Hole as the primary resolver and your ISP/router as the secondary. In the rare circumstance that the Pi-Hole device is down, you fallback and get the "normal" ISP DNS service.
Having two main servers hosting Pi-Home works great - until both of them are offline for any random reason. So I added a third Pi-Hole following Techno Tims easy to follow guide. By using keepalived and VIP I can update, restart and tinker with the two servers as much as I want. https://youtu.be/hPfk0qd4xEY
But what if all three go offline for any random reason? Are you planning to add a fourth?
A simpler solution: Deploy one Pi-Hole instance and then set clients to use Pi-Hole as the primary resolver and your ISP/router as the secondary. In the rare circumstance that the Pi-Hole device is down, you fallback and get the "normal" ISP DNS service.
The spec only says the dns IPs should be specified in preference order. Nothing says to treat it as primary and failover.
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.
In my mikrotik device I do have a small script to replace my DNS entry with Cloudflare in case it becomes unresponsive (and then back again once it's up). That is not very transparent though and devices will get errors until the switch happens.
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, reporting and setting too.
Cost is minimal and I’ve been happy to pay for it.
A local PiHole is probably faster, but NDNS is set and forget.