diff options
| author |  Miek Gieben <miek@miek.nl>
| 2020-02-06 19:28:53 +0100 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2020-02-06 19:28:53 +0100 |
| commit | c4fc5cb54ab262ca4d41dbb3b59d4f50b8486057 (patch) | |
| tree | fd48eb3d33594fe3d1afeb84df2bd5c94d344670 /plugin/forward/README.md | |
| parent | 1818df0d0633eb3446c7122007f0f96f3bc03c55 (diff) | |
| download | coredns-c4fc5cb54ab262ca4d41dbb3b59d4f50b8486057.tar.gz coredns-c4fc5cb54ab262ca4d41dbb3b59d4f50b8486057.tar.zst coredns-c4fc5cb54ab262ca4d41dbb3b59d4f50b8486057.zip | |
plugin/pkg/up: make default intervals shorter (#3651)
* plugin/pkg/up: make default intervals shorter
I think 15 min is too high, make this lower to react faster.
Signed-off-by: Miek Gieben <miek@miek.nl>
* Update README
Signed-off-by: Miek Gieben <miek@miek.nl>
Diffstat (limited to 'plugin/forward/README.md')
| -rw-r--r-- | plugin/forward/README.md | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/plugin/forward/README.md b/plugin/forward/README.md index 02da91bcc..77d8e181e 100644 --- a/plugin/forward/README.md +++ b/plugin/forward/README.md @@ -9,14 +9,14 @@ The *forward* plugin re-uses already opened sockets to the upstreams. It supports UDP, TCP and DNS-over-TLS and uses in band health checking. -When it detects an error a health check is performed. This checks runs in a loop, -starting with a *0.5s* interval and exponentially backing off with randomized intervals -up to *60s* for as long as the upstream reports unhealthy. The exponential backoff -will reset to *0.5s* after 15 minutes. Once healthy we stop health checking (until the next -error). The health checks use a recursive DNS query (`. IN NS`) to get upstream health. Any response -that is not a network error (REFUSED, NOTIMPL, SERVFAIL, etc) is taken as a healthy upstream. The -health check uses the same protocol as specified in **TO**. If `max_fails` is set to 0, no checking -is performed and upstreams will always be considered healthy. +When it detects an error a health check is performed. This checks runs in a loop, starting with +a *0.5s* interval and exponentially backing off with randomized intervals up to *15s* for as long +as the upstream reports unhealthy. The exponential backoff will reset to *0.5s* after 2 minutes. +Once healthy we stop health checking (until the next error). The health checks use a recursive +DNS query (`. IN NS`) to get upstream health. Any response that is not a network error (REFUSED, +NOTIMPL, SERVFAIL, etc) is taken as a healthy upstream. The health check uses the same protocol as +specified in **TO**. If `max_fails` is set to 0, no checking is performed and upstreams will always +be considered healthy. When *all* upstreams are down it assumes health checking as a mechanism has failed and will try to connect to a random upstream (which may or may not work). |