Mirrored_Repos/pihole-cloudsync
1
0
Fork 0
mirror of https://github.com/stevejenkins/pihole-cloudsync.git synced 2024-08-30 18:22:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Adding info on custom.list

Browse Source
This commit is contained in:
Steve Jenkins 2020-04-02 19:39:56 -07:00 committed by GitHub
parent 776e828ee4
commit 7d83df611f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
PIHOLE-V5-README.md
View File

@ -29,12 +29,12 @@ Follow the instructions in the <a target="_blank" href="https://github.com/steve
The **Shared Hosts Mode** option is still available in `pihole-cloudsync` for users who wish to remain on Pi-hole v4.
One of the new features of Pi-hole v5 is a **Custom DNS** tool that replicates `pihole-cloudsync`'s Shared Hosts Mode. Custom DNS entries can now be stored in Pi-hole's `gravity.db` file, which is then sychronized between your Primary and Secondary Pi-holes... along with the Custom DNS hosts.
One of the new features of Pi-hole v5 is a **Custom DNS** tool that replicates `pihole-cloudsync`'s Shared Hosts Mode. Custom DNS entries are now be stored in the `/etc/pihole/custom.list` file (and not in Pi-hole's new `gravity.db` file). When run in Pi-hole v5 mode, `pihole-cloudsync` also sychronizes this file between your Primary and Secondary Pi-holes so they can share Custom DNS host entries.
I recommend Pi-hole v5 users set the `enable_hosts` variable in the `pihole-cloudsync` script to **off** and manually migrate their shared hosts into Pi-hole v5 using the Custom DNS page in the admin UI.
I recommend Pi-hole v5 users set the `enable_hosts` variable in the `pihole-cloudsync` script to **off** and manually enter their shared hosts into their Primary Pi-hole v5 server by using the Custom DNS page in Pi-hole's admin web UI.
# Known Issues
The only issue I know of currently is that because Pi-hole now stores all its information in a single database file, that single file can easily be larger than the 50MB that Github recommends. I currently have it working just fine with a DB file that's currently over 70MB. Github allows it but throws a filesize warning when doing a "push." I may eventually get around to using GitHub's large file management system, but for now this works.
The only issue I know of currently is that because Pi-hole now stores nearly all its information in a single database file, that single file can easily be larger than the 50MB that Github recommends. I currently have it working just fine with a DB file that's currently over 70MB. Github allows it but throws a filesize warning when doing a "push." You can get rid of this error by adding GitHub's large file management system called "Git LFS," but you can't do it to only one or two hosts: **all** Secondary Pi-holes and your Primary Pi-hole must be configured to use Git LFS, or they will be unable to sync.
# Disclaimer
As always, you are totally responsible for anything this script does to your system. Whether it launches a nice game of Tic Tac Toe or global thermonuclear war, you're on your own. :)