mirror of
https://github.com/vmstan/gravity-sync.git
synced 2025-07-09 02:34:06 -04:00
Updated Home (markdown)
parent
d635aaed49
commit
33f55ee7f9
22
Home.md
22
Home.md
@ -4,24 +4,26 @@
|
||||
|
||||
What is better than a [Pi-hole](https://github.com/pi-hole/pi-hole) blocking ads via DNS on your network? That's right, two Pi-hole blocking ads on your network!
|
||||
|
||||
But if you have more than one Pi-hole in your network you'll want a simple way to keep the list configurations and local DNS settings identical between the two. That's Gravity Sync. With proper preparation it should only take a few minutes to install.
|
||||
But if you have more than one Pi-hole in your network you'll want a simple way to keep the list configurations and local DNS settings identical between the two. That's Gravity Sync. With proper preparation it should only take a few minutes to install. Ideally you set up Gravity Sync and forget about it -- and in the long term, it would be awesome if the Pi-hole team made this entire script unnecessary.
|
||||
|
||||
## Features
|
||||
|
||||
Gravity Sync will:
|
||||
|
||||
- Sync the Adlist database (allow/block list) configurations stored in `gravity.db` between multiple Pi-hole.
|
||||
- Sync the Local DNS Settings stored in `custom.list` between multiple Pi-hole.
|
||||
- Provide an easy way to keep this happening in the background.
|
||||
|
||||
Ideally you set up Gravity Sync and forget about it -- and in the long term, it would be awesome if the Pi-hole team made this entire script unnecessary.
|
||||
Gravity Sync the `gravity.db` database which includes:
|
||||
- Blocklist settings with status and comments.
|
||||
- Domain whitelist and blacklist along with status with comments.
|
||||
- Custom RegEx whitelist and blacklists.
|
||||
- Clients and groups along with any list assignments.
|
||||
- The Local DNS Settings feature in Pi-hole (These are stored in a separate `custom.list` file and this can optionally be disabled.)
|
||||
|
||||
### Limitations
|
||||
|
||||
Gravity Sync will **not**:
|
||||
|
||||
- Overwrite individual Pi-hole specific settings such as the device's network configuration, admin/API passwords/keys, upstream DNS resolvers, etc.
|
||||
- Keep DHCP settings or device leases synchronized.
|
||||
- Overwrite or sync device specific Pi-hole settings such as the local network configuration.
|
||||
- Overwrite or sync the Pi-hole admin/API passwords, not does not leverage these at all.
|
||||
- Overwrite or sync the upstream DNS resolvers, etc.
|
||||
- Overwrite or sync DHCP settings or device leases synchronized.
|
||||
- Overwrite or sync long term data, query logs, or statistics.
|
||||
|
||||
### Disclaimer
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user