Cutlery/gravity-sync
1
0
Fork 0
mirror of https://github.com/vmstan/gravity-sync.git synced 2025-07-09 02:34:06 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated Frequent Questions (markdown)

Michael Stanclift 2020-10-21 13:45:00 -05:00
parent 407319253b
commit c435cc1a85
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
Frequent-Questions.md

@ -4,6 +4,7 @@ These are frequent questions about Gravity Sync implementations. In addition to
- Redundancy. - Redundancy.
- If either Pi-hole fails or goes offline due to maintenance, the other Pi-hole continues to serve DNS to your network. - If either Pi-hole fails or goes offline due to maintenance, the other Pi-hole continues to serve DNS to your network.
- In most cases Pi-hole runs on a Raspberry Pi, which while awesome pieces of kit, are not exactly enterprise grade systems, and can have component failures (ex: cheap SD cards that cannot handle frequent write activity.)
- If you have your Pi-hole set up properly in the router with a single Pi-hole, there is often no other DNS server offered to clients. Some devices will get annoyed if you only have one DNS address. In some cases those devices will utilize hard coded backup servers, which often do not have any of the privacy protections/controls afforded by Pi-hole. - If you have your Pi-hole set up properly in the router with a single Pi-hole, there is often no other DNS server offered to clients. Some devices will get annoyed if you only have one DNS address. In some cases those devices will utilize hard coded backup servers, which often do not have any of the privacy protections/controls afforded by Pi-hole.
- Some people attempt to hand out public resolvers as a backup thinking it'll only be used if Pi-hole isn't available, which is not the case. (IOT devices are especially guilty of this.) - Some people attempt to hand out public resolvers as a backup thinking it'll only be used if Pi-hole isn't available, which is not the case. (IOT devices are especially guilty of this.)