Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-11-29 23:24:26 -05:00
Code Issues Packages Projects Releases Wiki Activity

doc update: run Makefile.doc (#3232)

Browse Source 
Add the new plugins ones: clouddns and sign. Remove federation from it.

Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
Miek Gieben
2019-08-30 15:58:25 +01:00
committed by GitHub
parent c466003a94
commit 25d85338e4
39 changed files with 436 additions and 156 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
man/coredns-k8s_external.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-K8S_EXTERNAL" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-K8S_EXTERNAL" 7 "August 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -12,11 +12,11 @@ service. This plugin is only useful if the \fIkubernetes\fP plugin is also loade
.PP
The plugin uses an external zone to resolve in-cluster IP addresses. It only handles queries for A,
AAAA and SRV records, all others result in NODATA responses. To make it a proper DNS zone it handles
AAAA and SRV records; all others result in NODATA responses. To make it a proper DNS zone, it handles
SOA and NS queries for the apex of the zone.
.PP
By default the apex of the zone will look like (assuming the zone used is \fB\fCexample.org\fR):
By default the apex of the zone will look like the following (assuming the zone used is \fB\fCexample.org\fR):
.PP
.RS
@@ -38,12 +38,12 @@ ns1.dns.example.org. 5 IN AAAA ....
.RE
.PP
Note we use the \fB\fCdns\fR subdomain to place the records the DNS needs (see the \fB\fCapex\fR directive). Also
Note that we use the \fB\fCdns\fR subdomain for the records DNS needs (see the \fB\fCapex\fR directive). Also
note the SOA's serial number is static. The IP addresses of the nameserver records are those of the
CoreDNS service.
.PP
The \fIk8s_external\fP plugin handles the subdomain \fB\fCdns\fR and the apex of the zone by itself, all other
The \fIk8s_external\fP plugin handles the subdomain \fB\fCdns\fR and the apex of the zone itself; all other
queries are resolved to addresses in the cluster.
.SH "SYNTAX"
@@ -61,7 +61,7 @@ k8s\_external [ZONE...]
.PP
If you want to change the apex domain or use a different TTL for the return records you can use
If you want to change the apex domain or use a different TTL for the returned records you can use
this extended syntax.
.PP
@@ -77,13 +77,13 @@ k8s\_external [ZONE...] {
.RE
.IP \(bu 4
\fBAPEX\fP is the name (DNS label) to use the apex records, defaults to \fB\fCdns\fR.
\fBAPEX\fP is the name (DNS label) to use for the apex records; it defaults to \fB\fCdns\fR.
.IP \(bu 4
\fB\fCttl\fR allows you to set a custom \fBTTL\fP for responses. The default is 5 (seconds).
.PP
Enable names under \fB\fCexample.org\fR to be resolved to in cluster DNS addresses.
Enable names under \fB\fCexample.org\fR to be resolved to in-cluster DNS addresses.
.PP
.RS
@@ -98,7 +98,7 @@ Enable names under \fB\fCexample.org\fR to be resolved to in cluster DNS address
.RE
.PP
With the Corefile above, the following Service will get an \fB\fCA\fR record for \fB\fCtest.default.example.org\fR with IP address \fB\fC192.168.200.123\fR.
With the Corefile above, the following Service will get an \fB\fCA\fR record for \fB\fCtest.default.example.org\fR with the IP address \fB\fC192.168.200.123\fR.
.PP
.RS