Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-10-27 00:04:15 -04: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-03-31 14:18:39 +00:00
parent d4cac0c43a
commit db1d4f91da
37 changed files with 80 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
man/coredns-acl.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-ACL" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-ACL" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -109,9 +109,9 @@ example.org {
If monitoring is enabled (via the \fIprometheus\fP plugin) then the following metrics are exported:
.IP \(bu 4
\fB\fCcoredns_request_block_count_total{server, zone}\fR - counter of DNS requests being blocked.
\fB\fCcoredns_dns_blocked_requests_total{server, zone}\fR - counter of DNS requests being blocked.
.IP \(bu 4
\fB\fCcoredns_request_allow_count_total{server}\fR - counter of DNS requests being allowed.
\fB\fCcoredns_dns_allowed_requests_total{server}\fR - counter of DNS requests being allowed.
.PP

2
man/coredns-any.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-ANY" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-ANY" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-auto.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-AUTO" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-AUTO" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

22
man/coredns-autopath.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-AUTOPATH" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-AUTOPATH" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -13,6 +13,9 @@ failures, the original reply is returned. Because \fIautopath\fP returns a reply
the original question it will add a CNAME that points from the original name (with the search path
element in it) to the name of this answer.
.PP
\fBNote\fP: There are several known issues. See section below.
.SH "SYNTAX"
.PP
.RS
@@ -39,7 +42,7 @@ If a plugin implements the \fB\fCAutoPather\fR interface then it can be used.
If monitoring is enabled (via the \fIprometheus\fP plugin) then the following metric is exported:
.IP \(bu 4
\fB\fCcoredns_autopath_success_count_total{server}\fR - counter of successfully autopath-ed queries.
\fB\fCcoredns_autopath_success_total{server}\fR - counter of successfully autopath-ed queries.
.PP
@@ -73,8 +76,19 @@ Use the search path dynamically retrieved from the \fIkubernetes\fP plugin.
.SH "KNOWN ISSUES"
.PP
In Kubernetes, \fIautopath\fP is not compatible with pods running from Windows nodes.
In Kubernetes, \fIautopath\fP can derive the wrong namespace of a client Pod (and therefore wrong search path)
in the following case. To properly build the search path of a client \fIautopath\fP needs to
know the namespace of the a Pod making a DNS request. To do this, it relies on the
\fIkubernetes\fP plugin's Pod cache to resolve the client's IP address to a Pod. The Pod cache is maintained by
an API watch on Pods. When Pod IP assignments change, the Kubernetes API notifies CoreDNS via the API watch.
However, that notification is not instantaneous. In the case that a Pod is deleted, and it's IP is
immediately provisioned to a Pod in another namespace, and that new Pod make a DNS lookup \fIbefore\fP the API watch
can notify CoreDNS of the change, \fIautopath\fP will resolve the IP to the previous Pod's namespace.
.PP
If the server side search ultimately results in a negative answer (e.g. \fB\fCNXDOMAIN\fR), then the client will fruitlessly search all paths manually, thus negating the \fIautopath\fP optimization.
In Kubernetes, \fIautopath\fP is not compatible with Pods running from Windows nodes.
.PP
If the server side search ultimately results in a negative answer (e.g. \fB\fCNXDOMAIN\fR), then the client will
fruitlessly search all paths manually, thus negating the \fIautopath\fP optimization.

12
man/coredns-azure.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-AZURE" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-AZURE" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -23,6 +23,7 @@ azure RESOURCE\_GROUP:ZONE... {
subscription SUBSCRIPTION\_ID
environment ENVIRONMENT
fallthrough [ZONES...]
access private
}
.fi
@@ -30,7 +31,7 @@ azure RESOURCE\_GROUP:ZONE... {
.IP \(bu 4
\fBRESOURCE_GROUP:ZONE\fP is the resource group to which the hosted zones belongs on Azure,
and \fBZONE\fP the zone that contains data.
and \fBZONE\fP the zone that contains data.
.IP \(bu 4
\fBCLIENT_ID\fP and \fBCLIENT_SECRET\fP are the credentials for Azure, and \fB\fCtenant\fR specifies the
\fBTENANT_ID\fP to be used. \fBSUBSCRIPTION_ID\fP is the subscription ID. All of these are needed
@@ -41,22 +42,25 @@ to access the data in Azure.
\fB\fCfallthrough\fR If zone matches and no record can be generated, pass request to the next plugin.
If \fBZONES\fP is omitted, then fallthrough happens for all zones for which the plugin is
authoritative.
.IP \(bu 4
\fB\fCaccess\fR specifies if the zone is \fB\fCpublic\fR or \fB\fCprivate\fR. Default is \fB\fCpublic\fR.
.SH "EXAMPLES"
.PP
Enable the \fIazure\fP plugin with Azure credentials for the zone \fB\fCexample.org\fR:
Enable the \fIazure\fP plugin with Azure credentials for private zones \fB\fCexample.org\fR, \fB\fCexample.private\fR:
.PP
.RS
.nf
example.org {
azure resource\_group\_foo:example.org {
azure resource\_group\_foo:example.org resource\_group\_foo:example.private {
tenant 123abc\-123abc\-123abc\-123abc
client 123abc\-123abc\-123abc\-234xyz
subscription 123abc\-123abc\-123abc\-563abc
secret mysecret
access private
}
}

2
man/coredns-bind.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-BIND" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-BIND" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-bufsize.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-BUFSIZE" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-BUFSIZE" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-cache.7
View File

@@ -107,7 +107,7 @@ If monitoring is enabled (via the \fIprometheus\fP plugin) then the following me
.PP
Cache types are either "denial" or "success". \fB\fCServer\fR is the server handling the request, see the
metrics plugin for documentation.
prometheus plugin for documentation.
.SH "EXAMPLES"
.PP

2
man/coredns-chaos.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-CHAOS" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-CHAOS" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-clouddns.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-CLOUDDNS" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-CLOUDDNS" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-debug.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-DEBUG" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-DEBUG" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-erratic.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-ERRATIC" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-ERRATIC" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-errors.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-ERRORS" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-ERRORS" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-etcd.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-ETCD" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-ETCD" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-file.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-FILE" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-FILE" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

10
man/coredns-forward.7
View File

@@ -165,16 +165,16 @@ If monitoring is enabled (via the \fIprometheus\fP plugin) then the following me
.IP \(bu 4
\fB\fCcoredns_forward_request_duration_seconds{to}\fR - duration per upstream interaction.
.IP \(bu 4
\fB\fCcoredns_forward_request_count_total{to}\fR - query count per upstream.
\fB\fCcoredns_forward_requests_total{to}\fR - query count per upstream.
.IP \(bu 4
\fB\fCcoredns_forward_response_rcode_count_total{to, rcode}\fR - count of RCODEs per upstream.
\fB\fCcoredns_forward_responses_total{to, rcode}\fR - count of RCODEs per upstream.
.IP \(bu 4
\fB\fCcoredns_forward_healthcheck_failure_count_total{to}\fR - number of failed health checks per upstream.
\fB\fCcoredns_forward_healthcheck_failures_total{to}\fR - number of failed health checks per upstream.
.IP \(bu 4
\fB\fCcoredns_forward_healthcheck_broken_count_total{}\fR - counter of when all upstreams are unhealthy,
\fB\fCcoredns_forward_healthcheck_broken_total{}\fR - counter of when all upstreams are unhealthy,
and we are randomly (this always uses the \fB\fCrandom\fR policy) spraying to an upstream.
.IP \(bu 4
\fB\fCmax_concurrent_reject_count_total{}\fR - counter of the number of queries rejected because the
\fB\fCmax_concurrent_rejects_total{}\fR - counter of the number of queries rejected because the
number of concurrent queries were at maximum.
Where \fB\fCto\fR is one of the upstream servers (\fBTO\fP from the config), \fB\fCrcode\fR is the returned RCODE
from the upstream.

6
man/coredns-grpc.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-GRPC" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-GRPC" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -95,9 +95,9 @@ If monitoring is enabled (via the \fIprometheus\fP plugin) then the following me
.IP \(bu 4
\fB\fCcoredns_grpc_request_duration_seconds{to}\fR - duration per upstream interaction.
.IP \(bu 4
\fB\fCcoredns_grpc_request_count_total{to}\fR - query count per upstream.
\fB\fCcoredns_grpc_requests_total{to}\fR - query count per upstream.
.IP \(bu 4
\fB\fCcoredns_grpc_response_rcode_count_total{to, rcode}\fR - count of RCODEs per upstream.
\fB\fCcoredns_grpc_responses_total{to, rcode}\fR - count of RCODEs per upstream.
and we are randomly (this always uses the \fB\fCrandom\fR policy) spraying to an upstream.

2
man/coredns-health.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-HEALTH" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-HEALTH" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-import.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-IMPORT" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-IMPORT" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-loadbalance.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-LOADBALANCE" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-LOADBALANCE" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-log.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-LOG" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-LOG" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-loop.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-LOOP" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-LOOP" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-metadata.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-METADATA" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-METADATA" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

12
man/coredns-metrics.7
View File

@@ -15,21 +15,19 @@ The following metrics are exported:
.IP \(bu 4
\fB\fCcoredns_build_info{version, revision, goversion}\fR - info about CoreDNS itself.
.IP \(bu 4
\fB\fCcoredns_panic_count_total{}\fR - total number of panics.
\fB\fCcoredns_panics_total{}\fR - total number of panics.
.IP \(bu 4
\fB\fCcoredns_dns_request_count_total{server, zone, proto, family}\fR - total query count.
\fB\fCcoredns_dns_requests_total{server, zone, proto, family, type}\fR - total query count.
.IP \(bu 4
\fB\fCcoredns_dns_request_duration_seconds{server, zone, type}\fR - duration to process each query.
.IP \(bu 4
\fB\fCcoredns_dns_request_size_bytes{server, zone, proto}\fR - size of the request in bytes.
.IP \(bu 4
\fB\fCcoredns_dns_request_do_count_total{server, zone}\fR - queries that have the DO bit set
.IP \(bu 4
\fB\fCcoredns_dns_request_type_count_total{server, zone, type}\fR - counter of queries per zone and type.
\fB\fCcoredns_dns_do_requests_total{server, zone}\fR - queries that have the DO bit set
.IP \(bu 4
\fB\fCcoredns_dns_response_size_bytes{server, zone, proto}\fR - response size in bytes.
.IP \(bu 4
\fB\fCcoredns_dns_response_rcode_count_total{server, zone, rcode}\fR - response per zone and rcode.
\fB\fCcoredns_dns_responses_total{server, zone, rcode}\fR - response per zone and rcode.
.IP \(bu 4
\fB\fCcoredns_plugin_enabled{server, zone, name}\fR - indicates whether a plugin is enabled on per server and zone basis.
@@ -52,8 +50,6 @@ The address family (\fB\fCfamily\fR) of the transport (1 = IP (IP version 4), 2
\fB\fCtype\fR which holds the query type. It holds most common types (A, AAAA, MX, SOA, CNAME, PTR, TXT,
NS, SRV, DS, DNSKEY, RRSIG, NSEC, NSEC3, IXFR, AXFR and ANY) and "other" which lumps together all
other types.
.IP \(bu 4
The \fB\fCresponse_rcode_count_total\fR has an extra label \fB\fCrcode\fR which holds the rcode of the response.
.PP

2
man/coredns-nsid.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-NSID" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-NSID" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-pprof.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-PPROF" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-PPROF" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-ready.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-READY" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-READY" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

11
man/coredns-reload.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-RELOAD" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-RELOAD" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -123,7 +123,7 @@ fail loading the new Corefile, abort and keep using the old process
.PP
After the aborted attempt to reload we are left with the old processes running, but the listener is
closed in step 1; so the health endpoint is broken. The same can happen in the prometheus metrics plugin.
closed in step 1; so the health endpoint is broken. The same can happen in the prometheus plugin.
.PP
In general be careful with assigning new port and expecting reload to work fully.
@@ -138,9 +138,14 @@ CoreDNS v1.7.0 and later does parse the Corefile and supports detecting changes
If monitoring is enabled (via the \fIprometheus\fP plugin) then the following metric is exported:
.IP \(bu 4
\fB\fCcoredns_reload_failed_count_total{}\fR - counts the number of failed reload attempts.
\fB\fCcoredns_reload_failed_total{}\fR - counts the number of failed reload attempts.
.IP \(bu 4
\fB\fCcoredns_reload_version_info{hash, value}\fR - record the hash value during reload.
.PP
Currently the type of \fB\fChash\fR is "md5", the \fB\fCvalue\fR is the returned hash value.
.SH "ALSO SEE"
.PP
See coredns-import(7) and corefile(5).

2
man/coredns-root.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-ROOT" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-ROOT" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-route53.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-ROUTE53" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-ROUTE53" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-sign.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-SIGN" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-SIGN" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-template.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-TEMPLATE" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-TEMPLATE" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-tls.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-TLS" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-TLS" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-trace.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-TRACE" 7 "December 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-TRACE" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

2
man/coredns-whoami.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-WHOAMI" 7 "January 2020" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-WHOAMI" 7 "March 2020" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP

4
man/coredns.1
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS" 1 "January 2020" "CoreDNS" "CoreDNS"
.TH "COREDNS" 1 "March 2020" "CoreDNS" "CoreDNS"
.SH "COREDNS"
.PP
@@ -58,5 +58,5 @@ Apache License 2.0
.SH "SEE ALSO"
.PP
Corefile(5) coredns-k8s_external(7) coredns-erratic(7) coredns-nsid(7) coredns-any(7) coredns-hosts(7) coredns-acl(7) coredns-dnssec(7) coredns-health(7) coredns-grpc(7) coredns-sign(7) coredns-file(7) coredns-root(7) coredns-auto(7) coredns-pprof(7) coredns-dnstap(7) coredns-clouddns(7) coredns-bufsize(7) coredns-tls(7) coredns-loadbalance(7) coredns-cache(7) coredns-whoami(7) coredns-bind(7) coredns-loop(7) coredns-import(7) coredns-chaos(7) coredns-template(7) coredns-azure(7) coredns-autopath(7) coredns-log(7) coredns-kubernetes(7) coredns-forward(7) coredns-debug(7) coredns-secondary(7) coredns-route53(7) coredns-transfer(7) coredns-errors(7) coredns-ready(7) coredns-reload(7) coredns-rewrite(7) coredns-metrics(7) coredns-metadata(7) coredns-etcd(7) coredns-cancel(7) coredns-trace(7).
Corefile(5) coredns-k8s_external(7) coredns-any(7) coredns-hosts(7) coredns-acl(7) coredns-dnssec(7) coredns-health(7) coredns-grpc(7) coredns-sign(7) coredns-kubernetes(7) coredns-file(7) coredns-nsid(7) coredns-auto(7) coredns-erratic(7) coredns-chaos(7) coredns-dnstap(7) coredns-pprof(7) coredns-bufsize(7) coredns-clouddns(7) coredns-loadbalance(7) coredns-log(7) coredns-root(7) coredns-whoami(7) coredns-dns64(7) coredns-loop(7) coredns-import(7) coredns-debug(7) coredns-template(7) coredns-azure(7) coredns-autopath(7) coredns-cache(7) coredns-forward(7) coredns-secondary(7) coredns-route53(7) coredns-transfer(7) coredns-bind(7) coredns-errors(7) coredns-ready(7) coredns-reload(7) coredns-rewrite(7) coredns-tls(7) coredns-metrics(7) coredns-metadata(7) coredns-etcd(7) coredns-cancel(7) coredns-trace(7).

2
man/corefile.5
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREFILE" 5 "December 2019" "CoreDNS" "CoreDNS"
.TH "COREFILE" 5 "March 2020" "CoreDNS" "CoreDNS"
.SH "NAME"
.PP