mirror of
https://github.com/coredns/coredns.git
synced 2025-10-27 08:14:18 -04:00
doc: fix generated manual pages (#3571)
Went over all generated manual pages and fixed some markdown issues, mostly escaping "_" to avoid underlining entire paragraphs. Some textual fixes in route53 and other cloud DNS plugins. Regenerated the markdown with mmark. Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
@@ -33,29 +33,23 @@ route53 [ZONE:HOSTED\_ZONE\_ID...] {
|
||||
domains (private vs. public hosted zone), CoreDNS does the lookup in the given order here.
|
||||
Therefore, for a non-existing resource record, SOA response will be from the rightmost zone.
|
||||
.IP \(bu 4
|
||||
\fBHOSTED\fIZONE\fPID\fP the ID of the hosted zone that contains the resource record sets to be
|
||||
\fBHOSTED_ZONE_ID\fP the ID of the hosted zone that contains the resource record sets to be
|
||||
accessed.
|
||||
.IP \(bu 4
|
||||
\fBAWS\fIACCESS\fPKEY_ID\fP and \fBAWS\fISECRET\fPACCESS_KEY\fP the AWS access key ID and secret access key
|
||||
\fBAWS_ACCESS_KEY_ID\fP and \fBAWS_SECRET_ACCESS_KEY\fP the AWS access key ID and secret access key
|
||||
to be used when query AWS (optional). If they are not provided, then coredns tries to access
|
||||
AWS credentials the same way as AWS CLI, e.g., environmental variables, AWS credentials file,
|
||||
instance profile credentials, etc.
|
||||
.IP \(bu 4
|
||||
\fB\fCcredentials\fR is used for reading the credential file and setting the profile name for a given
|
||||
zone.
|
||||
.IP \(bu 4
|
||||
\fBPROFILE\fP AWS account profile name. Defaults to \fB\fCdefault\fR.
|
||||
.IP \(bu 4
|
||||
\fBFILENAME\fP AWS credentials filename. Defaults to \fB\fC~/.aws/credentials\fR are used.
|
||||
\fB\fCcredentials\fR is used for reading the credential \fBFILENAME\fP and setting the \fBPROFILE\fP name for a given
|
||||
zone. \fBPROFILE\fP is the AWS account profile name. Defaults to \fB\fCdefault\fR. \fBFILENAME\fP is the
|
||||
AWS credentials filename, defaults to \fB\fC~/.aws/credentials\fR.
|
||||
.IP \(bu 4
|
||||
\fB\fCfallthrough\fR If zone matches and no record can be generated, pass request to the next plugin.
|
||||
If \fBZONES\fP is omitted, then fallthrough happens for all zones for which the plugin is
|
||||
authoritative. If specific zones are listed (for example \fB\fCin-addr.arpa\fR and \fB\fCip6.arpa\fR), then
|
||||
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
|
||||
|
||||
Reference in New Issue
Block a user