diff options
Diffstat (limited to 'man/coredns-forward.7')
| -rw-r--r-- | man/coredns-forward.7 | 18 |
1 files changed, 8 insertions, 10 deletions
diff --git a/man/coredns-forward.7 b/man/coredns-forward.7 index c4ee3ff06..865384416 100644 --- a/man/coredns-forward.7 +++ b/man/coredns-forward.7 @@ -1,5 +1,5 @@ .\" Generated by Mmark Markdown Processer - mmark.miek.nl -.TH "COREDNS-FORWARD" 7 "June 2020" "CoreDNS" "CoreDNS Plugins" +.TH "COREDNS-FORWARD" 7 "July 2020" "CoreDNS" "CoreDNS Plugins" .SH "NAME" .PP @@ -11,14 +11,12 @@ The \fIforward\fP plugin re-uses already opened sockets to the upstreams. It sup DNS-over-TLS and uses in band health checking. .PP -When it detects an error a health check is performed. This checks runs in a loop, starting with -a \fI0.5s\fP interval and exponentially backing off with randomized intervals up to \fI15s\fP for as long -as the upstream reports unhealthy. The exponential backoff will reset to \fI0.5s\fP after 2 minutes. -Once healthy we stop health checking (until the next error). The health checks use a recursive -DNS query (\fB\fC. IN NS\fR) 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 \fBTO\fP. If \fB\fCmax_fails\fR 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, performing each +check at a \fI0.5s\fP interval for as long as the upstream reports unhealthy. Once healthy we stop +health checking (until the next error). The health checks use a recursive DNS query (\fB\fC. IN NS\fR) +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 \fBTO\fP. If +\fB\fCmax_fails\fR is set to 0, no checking is performed and upstreams will always be considered healthy. .PP When \fIall\fP upstreams are down it assumes health checking as a mechanism has failed and will try to @@ -165,7 +163,7 @@ If monitoring is enabled (via the \fIprometheus\fP plugin) then the following me .IP \(bu 4 \fB\fCcoredns_forward_requests_total{to}\fR - query count per upstream. .IP \(bu 4 -\fB\fCcoredns_forward_responses_total{to}\fR - Counter of responses made per upstream. +\fB\fCcoredns_forward_responses_total{to}\fR - Counter of responses received per upstream. .IP \(bu 4 \fB\fCcoredns_forward_request_duration_seconds{to}\fR - duration per upstream interaction. .IP \(bu 4 |