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:
Miek Gieben 2019-12-29 13:35:17 +01:00 committed by GitHub
parent 92e0086c19
commit fc546cf129
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
17 changed files with 34 additions and 79 deletions

View file

@ -28,22 +28,18 @@ clouddns [ZONE:PROJECT_ID:HOSTED_ZONE_NAME...] {
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.
* **PROJECT_ID** the project ID of the Google Cloud project.
* **PROJECT\_ID** the project ID of the Google Cloud project.
* **HOSTED_ZONE_NAME** the name of the hosted zone that contains the resource record sets to be
* **HOSTED\_ZONE\_NAME** the name of the hosted zone that contains the resource record sets to be
accessed.
* `credentials` is used for reading the credential file.
* **FILENAME** GCP credentials file path (normally a .json file).
* `credentials` is used for reading the credential file from **FILENAME** (normally a .json file).
* `fallthrough` If zone matches and no record can be generated, pass request to the next plugin.
If **[ZONES...]** is omitted, then fallthrough happens for all zones for which the plugin is
authoritative. If specific zones are listed (for example `in-addr.arpa` and `ip6.arpa`), then
only queries for those zones will be subject to fallthrough.
* **ZONES** zones it should be authoritative for. If empty, the zones from the configuration block
## Examples
Enable clouddns with implicit GCP credentials and resolve CNAMEs via 10.0.0.1: