gravity-sync
unbound-docker-rpi
Our great sponsors
gravity-sync | unbound-docker-rpi | |
---|---|---|
121 | 6 | |
2,086 | 133 | |
- | - | |
4.4 | 5.4 | |
about 1 month ago | 14 days ago | |
Shell | Shell | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gravity-sync
-
Sync Local DNS and Lists on second pihole - latest way?
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.
- Have any idea ?
-
Two piholes and both with unbound?
As others have said both instances should be totally complete as the idea is if one goes offline you should still have another that functions exactly the same. I also run Gravity Sync in my environment, helps keep down the maintenance. When I whitelist a domain on one it syncs to the other within minutes, that kind of thing.
the github page has a really good walkthrough and explanation
-
Running PiHole on a second server
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
-
Using RPi for Pihole and remote access gateway
Run Pihole on both, if DNS goes down its painful. You can sync them with https://github.com/vmstan/gravity-sync
-
Who else doesn’t work in IT? What are you struggling with today.
Hmm, per their GitHub page, "Starting in Gravity Sync 4, replication of static DHCP assignments is now supported." (Found here: https://github.com/vmstan/gravity-sync/wiki/DHCP-Replication) -- But, as I stated before, I don't use PiHole for DHCP reservations so I can't comment on if it does or doesn't work.
-
What do you run your Pihole on?
They're separate DietPi installs with Gravity Sync to keep the lists synced, but they each maintain their own resolver (unbound) caches upstream, and all clients are configured for primary (Pihole) and secondary (Bihole) addresses, then a firewall rule on the router that forwards any traffic to port 53 (AKA DNS) to Pihole. They both feed metrics to a single host that gives me a custom dashboard. Secondary unit gets less traffic, so I also run NUT (Network UPS Tools) on it to control my APC UPS.
-
Homelab DNS?
Two pi holes with gravity sync? Then it wouldn't matter which one it hit https://github.com/vmstan/gravity-sync
-
Backup DNS if/when AdGuard container doesn't work
I decided to setup a 2 node replicated cluster with Pi-Hole using this excellent collection of scripts - https://github.com/vmstan/gravity-sync You can probably adopt it to use AdGuard since it has even simpler configuration than Pi-Hole. Here are some ideas how to do that here - https://github.com/AdguardTeam/AdGuardHome/issues/573
unbound-docker-rpi
-
My Raspberry Pi 4 Dashboard
- Unbound
-
Starting Unbound in a Docker Container
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 ```
-
Best Docker image to use to install Pi-hole (along with PiVPN and Unbound)?
mvance/unbound-rpi is a image that is updated regularly and used by many. The code he uses to create the image is here.
What are some alternatives?
docker-pihole-sync - A Docker Container To Sync Two Piholes
pihole-updatelists - Update Pi-hole's lists from remote sources easily
AdGuardHome - Network-wide ads & trackers blocking DNS server
pi-hole-keepalived
docker-pi-hole - Pi-hole in a docker container
uptime-kuma - A fancy self-hosted monitoring tool
docker-pihole-unbound - Run Pi-Hole + Unbound on Docker
Pi-hole - A black hole for Internet advertisements
whoogle-search - A self-hosted, ad-free, privacy-respecting metasearch engine
Pi-Hole-for-WSL1 - Ad-blocking DNS server for Windows • Unbound pre-configured • Deployment ready in minutes • Does not require hypervisor/docker
pi-hole-docker-compose - pi-hole-docker-compose
pihole-cloudsync - Syncs blocklists, blacklists, and whitelists across multiple Pi-holes using a private GitHub repo