2019-04-06 08:42:40 +01:00
. \" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-AUTOPATH" "7" "April 2019" "CoreDNS" "CoreDNS Plugins"
.SH NAME
.PP
\fI autopath\fP - allows for server-side search path completion.
.SH DESCRIPTION
.PP
If it sees a query that matches the first element of the configured search path, \fI autopath\fP will
follow the chain of search path elements and return the first reply that is not NXDOMAIN. On any
failures, the original reply is returned. Because \fI autopath\fP returns a reply for a name that wasn't
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.
.SH SYNTAX
.PP
.RS
2018-01-04 12:53:07 +00:00
.nf
2019-04-06 08:42:40 +01:00
autopath [ZONE...] RESOLV\- CONF
2018-01-04 12:53:07 +00:00
.fi
2019-04-06 08:42:40 +01:00
.RE
.IP \(bu 4
\fB ZONES\fP zones \fI autopath\fP should be authoritative for.
.IP \(bu 4
\fB RESOLV-CONF\fP points to a \fB \fC resolv.conf\fR like file or uses a special syntax to point to another
plugin. For instance \fB \fC @kubernetes\fR , will call out to the kubernetes plugin (for each
query) to retrieve the search list it should use.
.PP
If a plugin implements the \fB \fC AutoPather\fR interface then it can be used.
.SH METRICS
.PP
If monitoring is enabled (via the \fI prometheus\fP directive) then the following metric is exported:
.IP \(bu 4
\fB \fC coredns_autopath_success_count_total{server}\fR - counter of successfully autopath-ed queries.
.PP
The \fB \fC server\fR label is explained in the \fI metrics\fP plugin documentation.
.SH EXAMPLES
.PP
.RS
2018-01-04 12:53:07 +00:00
.nf
2019-04-06 08:42:40 +01:00
autopath my\- resolv.conf
2018-01-04 12:53:07 +00:00
.fi
2019-04-06 08:42:40 +01:00
.RE
2018-01-04 12:53:07 +00:00
2019-04-06 08:42:40 +01:00
.PP
Use \fB \fC my-resolv.conf\fR as the file to get the search path from. This file only needs so have one line:
\fB \fC search domain1 domain2 ...\fR
.PP
.RS
.nf
2018-01-04 12:53:07 +00:00
autopath @kubernetes
2019-04-06 08:42:40 +01:00
2018-01-04 12:53:07 +00:00
.fi
2019-04-06 08:42:40 +01:00
.RE
.PP
Use the search path dynamically retrieved from the \fI kubernetes\fP plugin.
.SH KNOWN ISSUES
.PP
In Kubernetes, \fI autopath\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 \fC NXDOMAIN\fR ), then the client will fruitlessly search all paths manually, thus negating the \fI autopath\fP optimization.