mirror of
https://github.com/pi-hole/docs.git
synced 2024-12-06 19:27:12 +01:00
Clarify each blocking mode name.
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
Pi-hole *FTL*DNS currently supports the following methods for blocking queries:
|
||||
Pi-hole *FTL*DNS currently supports the following modes for blocking queries:
|
||||
|
||||
* NULL (default and recommended)
|
||||
* IP-NODATA-AAAA
|
||||
@@ -58,7 +58,7 @@ doubleclick.net. 2 IN A 192.168.1.42
|
||||
|
||||
* May cause time-outs for HTTPS content even with properly configured firewall rules
|
||||
|
||||
## Pi-hole's full IP blocking
|
||||
## Pi-hole's full IP blocking mode
|
||||
|
||||
In `IP` mode, blocked queries will be answered with the local IP addresses of your Pi-hole (see [BLOCK_IP4](configfile.md#block_ipv4) and [BLOCK_IP6](configfile.md#block_ipv6) for additional options). To set this mode explicitly, set `BLOCKINGMODE=IP` in `/etc/pihole/pihole-FTL.conf`.
|
||||
|
||||
@@ -82,7 +82,7 @@ doubleclick.net. 2 IN AAAA fda2:2001:4756:0:ab27:beff:ef37:
|
||||
* May cause time-outs for HTTPS content even with properly configured firewall rules
|
||||
* May cause problems with alternating prefixes on IPv6 addresses (see `IP-AAAA-NODATA`)
|
||||
|
||||
## Pi-hole's NXDOMAIN blocking
|
||||
## Pi-hole's NXDOMAIN blocking mode
|
||||
|
||||
In `NXDOMAIN` mode, blocked queries will be answered with an empty response (i.e., there won't be an *answer* section) and status `NXDOMAIN`. A `NXDOMAIN` response should indicate that there is *no such domain* to the client making the query. To set this mode explicitly, set `BLOCKINGMODE=NXDOMAIN` in `/etc/pihole/pihole-FTL.conf`.
|
||||
|
||||
@@ -93,9 +93,9 @@ A blocked query would look like the following:
|
||||
;doubleclick.net. IN ANY
|
||||
```
|
||||
|
||||
**Advantages & Disadvantages:** This mode is similar to `NULL` blocking, but experiments suggest that clients may try to resolve blocked domains more often compared to `NULL` blocking.
|
||||
**Advantages & Disadvantages:** This mode is similar to `NULL` blocking mode, but experiments suggest that clients may try to resolve blocked domains more often compared to `NULL` blocking.
|
||||
|
||||
## Pi-hole's NODATA blocking
|
||||
## Pi-hole's NODATA blocking mode
|
||||
|
||||
In `NODATA` mode, blocked queries will be answered with an empty response (no answer section) and status `NODATA`. A `NODATA` response indicates that the domain exists, but there is no record for the requested query type. To set this mode explicitly, set `BLOCKINGMODE=NODATA` in `/etc/pihole/pihole-FTL.conf`.
|
||||
|
||||
@@ -106,6 +106,6 @@ A blocked query would look like the following:
|
||||
;doubleclick.net. IN ANY
|
||||
```
|
||||
|
||||
**Advantages & Disadvantages:** This mode is similar to `NXDOMAIN` blocking. Clients might have a better acceptance of `NODATA` replies compared to `NXDOMAIN` replies.
|
||||
**Advantages & Disadvantages:** This mode is similar to `NXDOMAIN` blocking mode. Clients might have a better acceptance of `NODATA` replies compared to `NXDOMAIN` replies.
|
||||
|
||||
{!abbreviations.md!}
|
||||
|
||||
Reference in New Issue
Block a user