Pull request: Configuration: imp cache ttl override doc

Updates AdguardTeam/AdGuardHome#4242.

Squashed commit of the following:

commit e7f24cfbe4dd49a3a4a68f4bbe86e2b027e9c30d
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Mon Feb 7 21:17:05 2022 +0300

    Configuration: fix

commit 8a5984c6b0d08a62eebc757bb94a877417ccda9e
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Mon Feb 7 21:08:59 2022 +0300

    Configuration: imp cache ttl override doc
Ainar Garipov 2022-02-07 21:20:35 +03:00
parent 32c0b17680
commit aff71f7491
1 changed files with 7 additions and 3 deletions

@ -394,9 +394,13 @@ Settings are stored in [YAML format](https://en.wikipedia.org/wiki/YAML), possib
1. `X-Real-IP`
1. `X-Forwarded-For`
- **DNS cache settings**
- `cache_size` — DNS cache size (in bytes)
- `cache_ttl_min` — Override TTL value (minimum) received from upstream server. This value can't larger than 3600 (1 hour).
- `cache_ttl_max` — Override TTL value (maximum) received from upstream server
- `cache_size` — DNS cache size (in bytes).
- `cache_ttl_min` — The minimum TTL override, in seconds. If the TTL of
a response from upstream is below this value, the TTL is replaced with it.
Must be less than or equal to `cache_ttl_max`.
- `cache_ttl_max` — The maximum TTL override, in seconds. If the TTL of
a response from upstream is above this value, the TTL is replaced with it.
Must be greater than or equal to `cache_ttl_min`.
- `cache_optimistic` (**since v0.107.0**) — Make AdGuard Home respond from
the cache even when the entries are expired and also try to refresh them.
The TTL for such responses is 60 seconds.