gravity-sync VS unbound-docker-rpi

I'm using https://github.com/vmstan/gravity-sync to sync my three piholes but I'll need to find a replacement if I upgrade to pihole v6.

OR I could implement https://github.com/vmstan/gravity-sync as it's last commit was a year ago but users still seem to be using it.

I run the split DHCP approach for years without issues. Having only one PiHole with DHCP Server doesn’t give you a fully redundant system. I don’t use Gravity Sync myself, but their wiki covers this case with examples: https://github.com/vmstan/gravity-sync/wiki/DHCP-Replication

the github page has a really good walkthrough and explanation

I don't have anything add to your question. But I recommend installing gravity-sync if you're going to run two piholes. It will sync up DNS entries (among other things) automatically to the second pihole when you add a entry one of them. https://github.com/vmstan/gravity-sync

If you go the 2 pihole route, I strongly recommend Gravity-Synch. https://github.com/vmstan/gravity-sync

- Unbound

In Pi-Hole, all the queries are sent to and answered by the Unbound docker container, as confirmed by the Pi-Hole logs. I am not seeing any query in Pi-Hole going outside my network for resolution, so I am stumped as to what the cause of this is. The best guess that I could come up with is that somehow Unbound got configured in forwarding mode instead of a recursive resolver. I am not an expert on networking or Unbound, so I am looking for anyone who has an idea as to how to solve this. If it helps, I used https://github.com/MatthewVance/unbound-docker-rpi as the docker image to set up unbound.

If your using a pi, you need to use the pi image. Also I remember that I created these files before deploying the container: config files for unbound * a-records.conf ```

mvance/unbound-rpi is a image that is updated regularly and used by many. The code he uses to create the image is here.