mirror of
				https://github.com/coredns/coredns.git
				synced 2025-10-27 00:04:15 -04:00 
			
		
		
		
	Doc: regenerate the man-pages (#2739)
A 'make -f Makefile.doc clean all'. Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
		| @@ -1,7 +1,7 @@ | ||||
| .\" generated with Ronn/v0.7.3 | ||||
| .\" http://github.com/rtomayko/ronn/tree/0.7.3 | ||||
| . | ||||
| .TH "COREDNS\-ETCD" "7" "February 2019" "CoreDNS" "CoreDNS plugins" | ||||
| .TH "COREDNS\-ETCD" "7" "March 2019" "CoreDNS" "CoreDNS plugins" | ||||
| . | ||||
| .SH "NAME" | ||||
| \fIetcd\fR \- enables reading zone data from an etcd version 3 instance\. | ||||
| @@ -10,7 +10,7 @@ | ||||
| The data in etcd instance has to be encoded as a message \fIhttps://github\.com/skynetservices/skydns/blob/2fcff74cdc9f9a7dd64189a447ef27ac354b725f/msg/service\.go#L26\fR like SkyDNS \fIhttps://github\.com/skynetservices/skydns\fR\. It should also work just like SkyDNS\. | ||||
| . | ||||
| .P | ||||
| The etcd plugin makes extensive use of the proxy plugin to forward and query other servers in the network\. | ||||
| The etcd plugin makes extensive use of the forward plugin to forward and query other servers in the network\. | ||||
| . | ||||
| .SH "SYNTAX" | ||||
| . | ||||
| @@ -61,7 +61,7 @@ etcd [ZONES\.\.\.] { | ||||
| \fBcredentials\fR is used to set the \fBUSERNAME\fR and \fBPASSWORD\fR for accessing the etcd cluster\. | ||||
| . | ||||
| .IP "\(bu" 4 | ||||
| \fBupstream\fR upstream resolvers to be used resolve external names found in etcd (think CNAMEs) pointing to external names\. If you want CoreDNS to act as a proxy for clients, you\'ll need to add the proxy plugin\. If no \fBADDRESS\fR is given, CoreDNS will resolve CNAMEs against itself\. \fBADDRESS\fR can be an IP address, and IP:port or a string pointing to a file that is structured as /etc/resolv\.conf\. | ||||
| \fBupstream\fR upstream resolvers to be used resolve external names found in etcd (think CNAMEs) pointing to external names\. If you want CoreDNS to act as a proxy for clients, you\'ll need to add the \fIforward\fR plugin\. If no \fBADDRESS\fR is given, CoreDNS will resolve CNAMEs against itself\. \fBADDRESS\fR can be an IP address, and IP:port or a string pointing to a file that is structured as /etc/resolv\.conf\. | ||||
| . | ||||
| .IP "\(bu" 4 | ||||
| \fBtls\fR followed by: | ||||
| @@ -114,7 +114,7 @@ This is the default SkyDNS setup, with everything specified in full: | ||||
|     prometheus | ||||
|     cache 160 skydns\.local | ||||
|     loadbalance | ||||
|     proxy \. 8\.8\.8\.8:53 8\.8\.4\.4:53 | ||||
|     forward \. 8\.8\.8\.8:53 8\.8\.4\.4:53 | ||||
| } | ||||
| . | ||||
| .fi | ||||
| @@ -134,7 +134,7 @@ Or a setup where we use \fB/etc/resolv\.conf\fR as the basis for the proxy and t | ||||
|         upstream | ||||
|     } | ||||
|     cache 160 skydns\.local | ||||
|     proxy \. /etc/resolv\.conf | ||||
|     forward \. /etc/resolv\.conf | ||||
| } | ||||
| . | ||||
| .fi | ||||
|   | ||||
		Reference in New Issue
	
	Block a user