Generate man-pages (#2439)

Almost 100% mechanical change, except the fact that import/import.md
is moved to import/README.md

No content changes.
Signed-off-by: Miek Gieben <miek@miek.nl>

man/coredns-auto.7

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREDNS\-AUTO" "7" "December 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-AUTO" "7" "January 2019" "CoreDNS" "CoreDNS plugins"
 .
 .SH "NAME"
 \fIauto\fR \- enables serving zone data from an RFC 1035\-style master file, which is automatically picked up from disk\.

man/coredns-etcd.7

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREDNS\-ETCD" "7" "October 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-ETCD" "7" "January 2019" "CoreDNS" "CoreDNS plugins"
 .
 .SH "NAME"
 \fIetcd\fR \- enables reading zone data from an etcd version 3 instance\.

man/coredns-federation.7

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREDNS\-FEDERATION" "7" "October 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-FEDERATION" "7" "January 2019" "CoreDNS" "CoreDNS plugins"
 .
 .SH "NAME"
 \fIfederation\fR \- enables federated queries to be resolved via the kubernetes plugin\.

man/coredns-file.7

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREDNS\-FILE" "7" "December 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-FILE" "7" "January 2019" "CoreDNS" "CoreDNS plugins"
 .
 .SH "NAME"
 \fIfile\fR \- enables serving zone data from an RFC 1035\-style master file\.

man/coredns-import.7

+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "COREDNS\-IMPORT" "7" "January 2019" "CoreDNS" "CoreDNS plugins"
+.
+.SH "NAME"
+\fIimport\fR \- include files or reference snippets from a Corefile\.
+.
+.SH "DESCRIPTION"
+The \fIimport\fR plugin can be used to incude files into the main configuration\. Another use it to reference predefined snippets\. Both can help to avoid some duplication\.
+.
+.P
+This is a unique directive in that \fIimport\fR can appear outside of a server block\. In other words, it can appear at the top of a Corefile where an address would normally be\.
+.
+.SH "SYNTAX"
+.
+.nf
+
+import PATTERN
+.
+.fi
+.
+.IP "\(bu" 4
+\fBPATTERN\fR is the file, glob pattern (\fB*\fR) or snippet to include\. Its contents will replace this line, as if that file\'s contents appeared here to begin with\.
+.
+.IP "" 0
+.
+.SH "FILES"
+You can use \fIimport\fR to include a file or files\. This file\'s location is relative to the Corefile\'s location\. It is an error if a specific file cannot be found, but an empty glob pattern is not an error\.
+.
+.SH "SNIPPETS"
+You can define snippets to be reused later in your Corefile by defining a block with a single\-token label surrounded by parentheses:
+.
+.IP "" 4
+.
+.nf
+
+(mysnippet) {
+    \.\.\.
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Then you can invoke the snippet with \fIimport\fR:
+.
+.IP "" 4
+.
+.nf
+
+import mysnippet
+.
+.fi
+.
+.IP "" 0
+.
+.SH "EXAMPLES"
+Import a shared configuration:
+.
+.IP "" 4
+.
+.nf
+
+\&\. {
+   import config/common\.conf
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Where \fBconfig/common\.conf\fR contains:
+.
+.IP "" 4
+.
+.nf
+
+prometheus
+errors
+log
+.
+.fi
+.
+.IP "" 0
+.
+.P
+This imports files found in the zones directory:
+.
+.IP "" 4
+.
+.nf
+
+import \.\./zones/*
+.
+.fi
+.
+.IP "" 0
+.
+.SH "ALSO SEE"
+See corefile(5)\.

man/coredns-kubernetes.7

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREDNS\-KUBERNETES" "7" "December 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-KUBERNETES" "7" "January 2019" "CoreDNS" "CoreDNS plugins"
 .
 .SH "NAME"
 \fIkubernetes\fR \- enables the reading zone data from a Kubernetes cluster\.

man/coredns-log.7

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREDNS\-LOG" "7" "December 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-LOG" "7" "January 2019" "CoreDNS" "CoreDNS plugins"
 .
 .SH "NAME"
 \fIlog\fR \- enables query logging to standard output\.
@@ -42,7 +42,7 @@ log [NAME] [FORMAT]
 \fBNAME\fR is the name to match in order to be logged
 .
 .IP "\(bu" 4
-\fBFORMAT\fR is the log format to use (default is Common Log Format)
+\fBFORMAT\fR is the log format to use (default is Common Log Format), \fB{common}\fR is used as a shortcut for the Common Log Format\. You can also use \fB{combined}\fR for a format that adds the query opcode \fB{>opcode}\fR to the Common Log Format\.
 .
 .IP "" 0
 .
@@ -73,7 +73,7 @@ The classes of responses have the following meaning:
 \fBsuccess\fR: successful response
 .
 .IP "\(bu" 4
-\fBdenial\fR: either NXDOMAIN or NODATA (name exists, type does not)
+\fBdenial\fR: either NXDOMAIN or nodata responses (Name exists, type does not)\. A nodata response sets the return code to NOERROR\.
 .
 .IP "\(bu" 4
 \fBerror\fR: SERVFAIL, NOTIMP, REFUSED, etc\. Anything that indicates the remote server is not willing to resolve the request\.
@@ -141,7 +141,13 @@ The following place holders are supported:
 \fB{>opcode}\fR: query OPCODE
 .
 .IP "\(bu" 4
-\fB{/[LABEL]}\fR: any metadata label is accepted as a place holder if it is enclosed between \fB{/\fR and \fB}\fR\. the place holder will be replaced by the corresponding metadata value or the default value \fB\-\fR if label is not defined\.
+\fB{common}\fR: the default Common Log Format\.
+.
+.IP "\(bu" 4
+\fB{combined}\fR: the Common Log Format with the query opcode\.
+.
+.IP "\(bu" 4
+\fB{/LABEL}\fR: any metadata label is accepted as a place holder if it is enclosed between \fB{/\fR and \fB}\fR, the place holder will be replaced by the corresponding metadata value or the default value \fB\-\fR if label is not defined\. See the \fImetadata\fR plugin for more information\.
 .
 .IP "" 0
 .
@@ -203,7 +209,7 @@ Custom log format, for all zones (\fB\.\fR)
 .IP "" 0
 .
 .P
-Only log denials for example\.org (and below to a file)
+Only log denials (NXDOMAIN and nodata) for example\.org (and below)
 .
 .IP "" 4
 .
@@ -220,14 +226,14 @@ Only log denials for example\.org (and below to a file)
 .IP "" 0
 .
 .P
-Log all queries which were not resolved successfully
+Log all queries which were not resolved successfully in the Combined Log Format\.
 .
 .IP "" 4
 .
 .nf
 
 \&\. {
-    log \. {
+    log \. {combined} {
         class denial error
     }
 }

man/coredns-loop.7

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREDNS\-LOOP" "7" "December 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-LOOP" "7" "January 2019" "CoreDNS" "CoreDNS plugins"
 .
 .SH "NAME"
 \fIloop\fR \- detect simple forwarding loops and halt the server\.
 .
 .SH "DESCRIPTION"
-The \fIloop\fR plugin will send a random probe query to ourselves and will then keep track of how many times we see it\. If we see it more than twice, we assume CoreDNS is looping and we halt the process\.
+The \fIloop\fR plugin will send a random probe query to ourselves and will then keep track of how many times we see it\. If we see it more than twice, we assume CoreDNS has seen a forwarding loop and we halt the process\.
 .
 .P
-The plugin will try to send the query for up to 30 seconds\. This is done to give CoreDNS enough time to start up\. Once a query has been successfully sent \fIloop\fR disables itself to prevent a query of death\.
+The plugin will try to send the query for up to 30 seconds\. This is done to give CoreDNS enough time to start up\. Once a query has been successfully sent, \fIloop\fR disables itself to prevent a query of death\.
 .
 .P
 The query sent is \fB<random number>\.<random number>\.zone\fR with type set to HINFO\.
@@ -46,25 +46,25 @@ After CoreDNS has started it stops the process while logging:
 .
 .nf
 
-plugin/loop: Forwarding loop detected in "\." zone\. Exiting\. See https://coredns\.io/plugins/loop#troubleshooting\. Probe query: "HINFO 5577006791947779410\.8674665223082153551\."\.
+plugin/loop: Loop (127\.0\.0\.1:55953 \-> :1053) detected for zone "\.", see https://coredns\.io/plugins/loop#troubleshooting\. Query: "HINFO 4547991504243258144\.3688648895315093531\."
 .
 .fi
 .
 .IP "" 0
 .
 .SH "LIMITATIONS"
-This plugin only attempts to find simple static forwarding loops at start up time\. To detect a loop, all of the following must be true
+This plugin only attempts to find simple static forwarding loops at start up time\. To detect a loop, the following must be true:
 .
 .IP "\(bu" 4
 the loop must be present at start up time\.
 .
 .IP "\(bu" 4
-the loop must occur for at least the \fBHINFO\fR query type\.
+the loop must occur for the \fBHINFO\fR query type\.
 .
 .IP "" 0
 .
 .SH "TROUBLESHOOTING"
-When CoreDNS logs contain the message \fBForwarding loop detected \.\.\.\fR, this means that the \fBloop\fR detection plugin has detected an infinite forwarding loop in one of the upstream DNS servers\. This is a fatal error because operating with an infinite loop will consume memory and CPU until eventual out of memory death by the host\.
+When CoreDNS logs contain the message \fBLoop \.\.\. detected \.\.\.\fR, this means that the \fBloop\fR detection plugin has detected an infinite forwarding loop in one of the upstream DNS servers\. This is a fatal error because operating with an infinite loop will consume memory and CPU until eventual out of memory death by the host\.
 .
 .P
 A forwarding loop is usually caused by:

man/coredns-route53.7

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREDNS\-ROUTE53" "7" "December 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-ROUTE53" "7" "January 2019" "CoreDNS" "CoreDNS plugins"
 .
 .SH "NAME"
 \fIroute53\fR \- enables serving zone data from AWS route53\.

man/coredns-secondary.7

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREDNS\-SECONDARY" "7" "October 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-SECONDARY" "7" "January 2019" "CoreDNS" "CoreDNS plugins"
 .
 .SH "NAME"
 \fIsecondary\fR \- enables serving a zone retrieved from a primary server\.

man/coredns-template.7

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREDNS\-TEMPLATE" "7" "October 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-TEMPLATE" "7" "January 2019" "CoreDNS" "CoreDNS plugins"
 .
 .SH "NAME"
 \fItemplate\fR \- allows for dynamic responses based on the incoming query\.

man/corefile.5

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREFILE" "5" "August 2018" "CoreDNS" "CoreDNS"
+.TH "COREFILE" "5" "January 2019" "CoreDNS" "CoreDNS"
 .
 .SH "NAME"
 \fBcorefile\fR
@@ -34,7 +34,7 @@ The optional \fBSCHEME\fR defaults to \fBdns://\fR, but can also be \fBtls://\fR
 The optional \fBPORT\fR controls on which port the server will bind, this default to 53\. If you use a port number here, you \fIcan\'t\fR override it with \fB\-dns\.port\fR (coredns(1))\.
 .
 .P
-Specifying a \fBZONE\fR \fIand\fR \fBPORT\fR combination multiple time for \fIdifferent\fR servers will lead to an error on startup\.
+Specifying a \fBZONE\fR \fIand\fR \fBPORT\fR combination multiple times for \fIdifferent\fR servers will lead to an error on startup\.
 .
 .P
 When a query comes in, it is matched again all zones for all servers, the server with the longest match on the query name will receive the query\.
@@ -49,7 +49,7 @@ Comments are allowed and begin with an unquoted hash \fB#\fR and continue to the
 Environment variables are supported and either the Unix or Windows form may be used: \fB{$ENV_VAR_1}\fR or \fB{%ENV_VAR_2%}\fR\.
 .
 .P
-You can use the \fBimport\fR "plugin" to include parts of other files, see \fIhttps://coredns\.io/explugins/import\fR\.
+You can use the \fBimport\fR "plugin" to include parts of other files\.
 .
 .P
 If CoreDNS can’t find a Corefile to load it loads the following builtin one:
@@ -66,6 +66,29 @@ If CoreDNS can’t find a Corefile to load it loads the following builtin one:
 .
 .IP "" 0
 .
+.SH "IMPORT"
+You can use the \fBimport\fR "plugin" to include parts of other files, see \fIhttps://coredns\.io/plugins/import\fR\.
+.
+.SH "SNIPPETS"
+If you want to reuse a snippet you can define one with and then use it with \fIimport\fR\.
+.
+.IP "" 4
+.
+.nf
+
+(mysnippet) {
+    log
+    whoami
+}
+
+\. {
+    import mysnippet
+}
+.
+.fi
+.
+.IP "" 0
+.
 .SH "EXAMPLES"
 The \fBZONE\fR is root zone \fB\.\fR, the \fBPLUGIN\fR is chaos\. The chaos plugin takes an argument: \fBCoreDNS\-001\fR\. This text is returned on a CH class query: \fBdig CH txt version\.bind @localhost\fR\.
 .
@@ -166,4 +189,4 @@ CoreDNS Authors\.
 Apache License 2\.0
 .
 .SH "SEE ALSO"
-The manual page for CoreDNS: coredns(1) and more documentation on \fIhttps://coredns\.io\fR\.
+The manual page for CoreDNS: coredns(1) and more documentation on \fIhttps://coredns\.io\fR\. Also see the \fIimport\fR \fIhttps://coredns\.io/plugins/import\fR\'s documentation\.