pihole-cloudsync VS pi-hole-keepalived

OR I could implement https://github.com/stevejenkins/pihole-cloudsync but this had the last commit 3 years ago so no idea if it works still

pihole-cloudsync is another fantastic option. I’ve been running it without issue syncing bidirectionally between 6 pinholes for nearly 5 years

Prior to now I’ve been using steve jenkins’ repo, which has been forked by other users to support docker based Pi-hole , however this isn’t working as consistently as I’d like (which could be my issue re setup), but as that repo has not seen changes for quite a while , it might be better to try the other first.

I use a similar thing, actually - https://github.com/stevejenkins/pihole-cloudsync I push the lists from my primary into github and then pull it from github to my secondary.

Don't forget to mention pihole cloudysnc https://github.com/stevejenkins/pihole-cloudsync

I was also thinking of using something like https://github.com/stevejenkins/pihole-cloudsync to sync up the blocklists so whatever I lists I change on mine will also reflect on theirs.

Just set this up with pihole-cloudsync an hour ago. It’s pretty straightforward, though relies on GitHub for cloud sync. You can also set it up to sync regularly unassisted.

pihole-cloudsync

Add keepalived to the equation and you have a single dns IP address with failover. Basically, keepalived points both Pi-holes towards a virtual IP address. If your “primary” goes down, keepalived will push your “secondary” to the virtual ip, and your devices will keep on ticking.