From 7e53996df81219ebc926bf47ec09edc379de8fcd Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Thu, 21 May 2020 21:19:46 -0500 Subject: [PATCH] Clarify blocklist --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a600b4f..3a1fc33 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ For more information visit [https://vmstan.com/gravity-sync/](https://vmstan.com If you have more than one Pi-hole (PH) in your network and you want to keep the list configurations identical between the two, you've come to the right place. -The script assumes you have one "primary" PH as the place you make all your configuration changes through the Web UI, doing things such as; manual whitelisting, adding blocklists, device/group management, and other list settings. The script will pull the configuration of the primary PH to the secondary. +The script assumes you have one "primary" PH as the place you make all your configuration changes through the Web UI, doing things such as; manual whitelisting, adding blocklists, device/group management, and other list settings. The script will pull the configuration of the primary PH to the secondary. It will also bring over the downloaded blocklist files after a `pihole -g` update on the primary, so you do not need to reach out to all your blocklist hosts for updates after syncing. It will **not** overwrite device specific settings such as local network configuration, admin/API passwords/keys, upstream DNS resolvers, etc. It will also **not** keep DHCP settings or device leases synchronized.