Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-12-06 02:15:11 -05:00
Code Issues Packages Projects Releases Wiki Activity

auto make -f Makefile.doc

Browse Source
This commit is contained in:
coredns-auto-go-mod-tidy[bot]
2020-07-23 07:40:36 +00:00
parent c86be3428a
commit 5b09d62f86
47 changed files with 61 additions and 58 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
man/coredns-forward.7
View File

@@ -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