Question on redundancy with rpi4 and Pihole

[Trooper_ish]

##edit: see Risk’s post below…##

@bot

as simple as setting the second pi as the routers second DNS server

This.

Set a second one as a second DNS server, and the clients will check it when the first pi goes down.

But, the clients might try the first one for a while, even after it dies, so suddenly “the internet got really slow” as the clients keep querying the first one first.

When that happens, the quickest thing would be to change pi2’s IP to pi1’s IP address, and when you recondition pi1, set it up as pi2…

To extend the life of the pi’s, I would suggest moving the logs to Ram:

azlux/log2ram

which reduces the strain on the OS stick.

Also, if you are using pi4,

Update the firmware, and you can use a cheap, small SSD- it will last longer than a SD card, even a $5 or $10 cheap ssd, like a 60gb or small ssd (larger would work, but save less money) and a cheapish sata to USB cable (might want to look ar UASP cables if it’s gonna be used for storage too)

You might have a look at the link for more ideas:

Infrastructure Series -- Taking DNS One Step Further - Full DNS Server infrastructure

So we are all familiar with my other post: Infrastructure Series -- Recursive DNS and Adblocking DoT w/NGINX Obligatory shill of blog stream post: Phaselockedloopable- PLL’s continued exploration of networking, self-hosting and decoupling from big tech As always check for updates in the second post DoT is great but it can be messed with or blocked by denying port 853. So what can we do to get around this and what are our options. Well lets make a full set of architecture. Lets do DoH and normal DNS via our NGINX server! Why not right? We already have the setup and the backbone. Standard DNS A standard DNS server is easy to host given our DoT setup. It really is as simple as created a entry for port 53 and TCP streaming it via the stream block. (please refer to DoT post) # Standard DNS Server server { listen 53; listen [::]:53; error_log /var/log/nginx/dns53.log info; proxy_pass dns; } Open the port on your node and DNS will be functioning when you point at its addresses after you restart nginx. It really is that simple. DoH + DoQ We are going to use the DoH-Proxy software designed by facebook-experimental working group. Its an open source python handler dont worry. The first thing you will need to do is install (on the node proxy system in my case) (not necessarily advised) the software via python pip3 sudo pip3 install doh-proxy optionally you may git grab the latest upstream at git+https://github.com/facebookexperimental/doh-proxy.git but that may not be the most stable implementation. We want doh-proxy to have its own user so create a user for it. So we execute the following command adduser -r doh-proxy -d /var/lib/doh-proxy -c 'DOH Proxy server' -s /sbin/nologin -U *please note the nologin path may change from system to system All at once we can create tghe directories necessary mkdir /var/lib/doh-proxy && chown doh-proxy: /var/lib/doh-proxy && chown 700 /var/lib/doh-proxy Thats pretty much it on the directories and user/…