mirror of
https://github.com/pi-hole/docs.git
synced 2024-12-06 19:27:12 +01:00
Add new PIHOLE_PTR=HOSTNAME option documentation
Signed-off-by: DL6ER <dl6er@dl6er.de>
This commit is contained in:
@@ -124,9 +124,13 @@ 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'}
|
||||
#### `PIHOLE_PTR=PI.HOLE|HOSTNAME|NONE` (PR [#1111](https://github.com/pi-hole/FTL/pull/1111), [#1164](https://github.com/pi-hole/FTL/pull/1164)) {#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.
|
||||
Controls whether and how FTL will reply with for address for which a local interface exists. Valid options are:
|
||||
|
||||
- `PI.HOLE` (the default) respond with `pi.hole`
|
||||
- `HOSTNAME` serve the machine's global hostname
|
||||
- `NONE` Pi-hole will **not** respond automatically on PTR requests to local interface addresses. Ensure `pi.hole` and/or hostname records exist elsewhere.
|
||||
|
||||
#### `DELAY_STARTUP=0` (PR [#716](https://github.com/pi-hole/FTL/pull/716)) {#delay_startup data-toc-label='Delay resolver startup'}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user