From 9183d921ce6d9d868e844252edb34367facea7ef Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Wed, 21 Oct 2020 13:46:13 -0500 Subject: [PATCH] Updated Frequent Questions (markdown) --- Frequent-Questions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Frequent-Questions.md b/Frequent-Questions.md index e92902e..a80d0ea 100644 --- a/Frequent-Questions.md +++ b/Frequent-Questions.md @@ -4,7 +4,7 @@ These are frequent questions about Gravity Sync implementations. In addition to - Redundancy. - 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.) +- The most attractive way for people to leverage Pi-hole is 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. - 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.)