From ded0523a0ed8732aa6e6d280e32bb4e62bd7e4b7 Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Fri, 15 Apr 2022 22:52:51 -0500 Subject: [PATCH] Updated Frequent Questions (markdown) --- Frequent-Questions.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Frequent-Questions.md b/Frequent-Questions.md index 6788d49..552593f 100644 --- a/Frequent-Questions.md +++ b/Frequent-Questions.md @@ -8,6 +8,7 @@ Redundancy. - The most attractive way for people to leverage Pi-hole is on a Raspberry Pi, which are not exactly "enterprise grade" systems, and usually have cheap SD cards that can burn out due to due to frequent write activity. - If you have your Pi-hole setup as the only DNS target, some devices will get annoyed and commonly will utilize hard coded backup servers, from public DNS resolvers which do not have any of the privacy protections afforded by Pi-hole. - In some cases people intentionally set those public resolvers as a backup entry in DHCP, thinking it'll only be used if Pi-hole isn't available, **which is not the case.** +- Home automation, smart TVs/speakers and other IOT devices are the most common offenders here. (In my own environment approximately 10% of queries happen against the second DNS resolver, but it frequently has a much higher blocking rate over the primary.) ### Do you merge the statistics and logs from each Pi-hole?