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 1 Packages Projects Releases Wiki Activity

Add missing FTL config options (#564)

Browse Source 
* Add missing FTL config options

Signed-off-by: yubiuser <ckoenig@posteo.de>

* Fix TOC

Signed-off-by: yubiuser <ckoenig@posteo.de>

* Remove  from Telnet API label

Signed-off-by: yubiuser <ckoenig@posteo.de>

* Address reviewers comments

Signed-off-by: yubiuser <ckoenig@posteo.de>

* Empty

Signed-off-by: yubiuser <ckoenig@posteo.de>
This commit is contained in:
yubiuser
2021-09-14 09:25:57 +02:00
committed by GitHub
parent 6db62978a9
commit 11bde099eb
1 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ftldns/configfile.md
+14 -1
View File
@@ -59,6 +59,11 @@ When the gravity database is locked/busy, how should Pi-hole handle queries?
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.
#### `MOZILLA_CANARY=true|false` (PR [#1148](https://github.com/pi-hole/FTL/pull/1148)) {#mozilla_canary data-toc-label='Mozilla canary domain handling'}
Should Pi-hole always replies with `NXDOMAIN` to `A` and `AAAA` queries of `use-application-dns.net` to disable Firefox automatic DNS-over-HTTP?
This is following the recommendation on [https://support.mozilla.org/en-US/kb/configuring-networks-disable-dns-over-https](https://support.mozilla.org/en-US/kb/configuring-networks-disable-dns-over-https)
---
### Statistics settings
@@ -109,6 +114,10 @@ Should `FTL` try to resolve IPv6 addresses to hostnames?
Should `FTL` try to resolve IPv4 addresses to hostnames?
#### `PIHOLE_PTR=true|false` (PR [#1111](https://github.com/pi-hole/FTL/pull/1111)) {#pihole_ptr data-toc-label='Pi-hole PTR'}
FTL will reply with `pi.hole` for every address for which a local interface exists. When you set this option to `false`, Pi-hole will **not** respond with `pi.hole` on PTR requests to local interface addresses.
#### `DELAY_STARTUP=0` (PR [#716](https://github.com/pi-hole/FTL/pull/716)) {#delay_startup data-toc-label='Delay resolver startup'}
In certain configurations, you may want FTL to wait a given amount of time before trying to start the DNS revolver. This is typically found when network interfaces appear only late during system startup and the interface startup priorities are configured incorrectly. This setting takes any integer value between 0 and 300 seconds.
@@ -263,7 +272,7 @@ Controls if *FTL*DNS should print extended details about regex matching into `pi
**[More details](../regex/overview.md)**
#### `DEBUG_API=false|true` {#debug_api data-toc-label='Telnet API'}
#### `DEBUG_API=false|true` {#debug_api data-toc-label='Telnet'}
Print extra debugging information during telnet API calls. Currently only used to send extra information when getting all queries.
@@ -311,6 +320,10 @@ Log information regarding FTL's embedded event handling queue.
Log information about script helpers, e.g., due to `dhcp-script`.
#### `ADDR2LINE=true|false` (PR [#774](https://github.com/pi-hole/FTL/pull/774)) {#addr2line data-toc-label='Addr2Line'}
Should FTL translate its own stack addresses into code lines during the bug backtrace? This improves the analysis of crashed significantly. It is recommended to leave the option enabled. This option should only be disabled when `addr2line` is known to not be working correctly on the machine because, in this case, the malfunctioning `addr2line` can prevent from generating any backtrace at all.
#### `DEBUG_EXTRA=false|true` (PR [#994](https://github.com/pi-hole/FTL/pull/994)) {#debug_extra data-toc-label='Misc.'}
Temporary flag that may print additional information. This debug flag is meant to be used whenever needed for temporary investigations. The logged content may change without further notice at any time.