mechanical: run: go gen and make -f Makefile.doc (#3104)

no manual updates; just generated stuff.

Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
Miek Gieben
2019-08-09 16:40:30 +01:00
committed by Yong Tang
parent 1bb753c5b0
commit 6a6e9a9b33
4 changed files with 98 additions and 3 deletions

View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-ROUTE53" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-ROUTE53" 7 "August 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -22,6 +22,7 @@ route53 [ZONE:HOSTED\_ZONE\_ID...] {
aws\_access\_key [AWS\_ACCESS\_KEY\_ID AWS\_SECRET\_ACCESS\_KEY]
credentials PROFILE [FILENAME]
fallthrough [ZONES...]
refresh DURATION
}
.fi
@@ -54,6 +55,14 @@ only queries for those zones will be subject to fallthrough.
.IP \(bu 4
\fBZONES\fP zones it should be authoritative for. If empty, the zones from the configuration
block.
.IP \(bu 4
\fB\fCrefresh\fR can be used to control how long between record retrievals from Route 53. It requires
a duration string as a parameter to specify the duration between update cycles. Each update
cycle may result in many AWS API calls depending on how many domains use this plugin and how
many records are in each. Adjusting the update frequency may help reduce the potential of API
rate-limiting imposed by AWS.
.IP \(bu 4
\fBDURATION\fP A duration string. Defaults to \fB\fC1m\fR. If units are unspecified, seconds are assumed.
.SH "EXAMPLES"
@@ -118,3 +127,19 @@ Enable route53 with multiple hosted zones with the same domain:
.fi
.RE
.PP
Enable route53 and refresh records every 3 minutes
.PP
.RS
.nf
\&. {
route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7 {
refresh 3m
}
}
.fi
.RE