(If your router supports using ssh keys for authentication all the better). My suggestion would be to have the script connect to your router by ssh and change the router DNS settings back away from your Pi-hole that way. The router settings away from the Pi-hole. You could set up a script on one (or both, why not?) of your BBBs and have them test dns connectivity periodically, and if it goes down for longer than you consider acceptable change It should certainly be possible with the gear you describe. As such, any recos for implementing such a watchdog scheme? The point is that I plan to have one BBB run Pi Hole, and I could setup the other BBB to act as a watchdog over Pi Hole's health on BBB 1. I have two BeagleBone Black Rev C's (BBB) running various home automation things. Hence, I ask the community: is there a good solution to automatically revert to "normal" DNS resolution if Pi Hole dies?Ĭan a router with Tomato or some other popular 3rd party OSS be set to periodically check Pi Hole's "health", and "revert" if the Pi Hole gets sick? HOWEVER, I just know Murphy's Law will strike eventually: the Pi Hole will die when I'm away on a business trip and no one in my household will be able to fix the Pi Hole device, or login into the main router to set the DNS setting back to 8.8.8.8 to restore internet visibility until I get home to sort things out. I really like the idea having Pi Hole be the DNS resolver for my network because it "automatically" covers the plethora of devices around the house all at once.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |