From e333932705015b121f804dd0ff826267120be9fe Mon Sep 17 00:00:00 2001 From: DL6ER Date: Thu, 17 May 2018 16:55:16 +0200 Subject: [PATCH] Worked on review comments Signed-off-by: DL6ER --- docs/ftldns/blockingmode.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/ftldns/blockingmode.md b/docs/ftldns/blockingmode.md index 8a86e4f..3735cbf 100644 --- a/docs/ftldns/blockingmode.md +++ b/docs/ftldns/blockingmode.md @@ -2,7 +2,7 @@ Pi-hole *FTL*DNS supports two different methods for blocking queries. Both have This setting can be updated by sending `SIGHUP` to `pihole-FTL` (`sudo killall -SIGHUP pihole-FTL`). -## Pi-hole's IP based blocking +## Pi-hole's IP blocking `/etc/pihole/pihole-FTL.conf` setting: ``` BLOCKINGMODE=IP @@ -25,7 +25,7 @@ doubleclick.net. 2 IN AAAA fda2:2001:4756:0:ab27:beff:ef37: - Requires a webserver to run on your Pi-hole - May cause time-outs for HTTPS content even with properly configured firewall rules -## Pi-hole's NXDOMAIN based blocking +## Pi-hole's NXDOMAIN blocking `/etc/pihole/pihole-FTL.conf` setting: ``` BLOCKINGMODE=NXDOMAIN @@ -45,13 +45,13 @@ Queries DNS queries will be answered with an empty response (no answer section) ##### Disadvantage - Blocking page cannot be shown and whitelisting has to be performed from the dashboard or CLI -## Pi-hole's `NULL` IP based blocking +## Pi-hole's unspecified IP blocking `/etc/pihole/pihole-FTL.conf` setting: ``` BLOCKINGMODE=NULL ``` -Queries will be answered with the local IP addresses of your Pi-hole (as configured in your `setupVars.conf` file) +Queries will be answered with the unspecified address ``` ;; QUESTION SECTION: ;doubleclick.net. IN ANY