pi-hole/docs
1
0
Fork 0
mirror of https://github.com/pi-hole/docs.git synced 2024-12-06 19:27:12 +01:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Fix quotes

Browse Source 
Signed-off-by: yubiuser <ckoenig@posteo.de>
This commit is contained in:
yubiuser
2021-08-23 18:35:51 +02:00
parent 167a64eadd
commit 6bc37226bb
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ftldns/configfile.md
+2 -2
View File
@@ -48,7 +48,7 @@ When using `IP` blocking mode, `FTL` determines the address of the interface a q
When using `IP` blocking mode, `FTL` determines the address of the interface a query arrived on. We then use this IP address in the blocked reply. This setting can be used to overwrite the replied IPv6 (`AAAA`) address.
#### `REPLY_WHEN_BUSY=DROP|ALLOW|BLOCK|REFUSE (PR [#1156](https://github.com/pi-hole/FTL/pull/1156)) {#reply_when_busy data-toc-label='Database busy reply'}
#### `REPLY_WHEN_BUSY=DROP|ALLOW|BLOCK|REFUSE` (PR [#1156](https://github.com/pi-hole/FTL/pull/1156)) {#reply_when_busy data-toc-label='Database busy reply'}
When the gravity database is locked/busy, how should Pi-hole handle queries?
@@ -57,7 +57,7 @@ When the gravity database is locked/busy, how should Pi-hole handle queries?
- `REFUSE` - refuse all queries which arrive while the database is busy
- `DROP` - just drop the queries, i.e., never reply to them at all.
Despite `REFUSE` sounding similar to `DROP`, it turned out that many clients will just immediately retry, causing up to several thousands of queries per second. This does not happen in DROP mode.
Despite `REFUSE` sounding similar to `DROP`, it turned out that many clients will just immediately retry, causing up to several thousands of queries per second. This does not happen in `DROP` mode.
---