diff options
| author |  Miek Gieben <miek@miek.nl>
| 2019-04-06 08:43:19 +0100 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2019-04-06 08:43:19 +0100 |
| commit | 5a4e4d92eff368a552fb01dd5a2874d3834664de (patch) | |
| tree | 8bce1a30c3038c2dd2cc7e0de31bbee83803881f | |
| parent | f8aa208cc00edf5ed231979210f8996bf318627d (diff) | |
| download | coredns-5a4e4d92eff368a552fb01dd5a2874d3834664de.tar.gz coredns-5a4e4d92eff368a552fb01dd5a2874d3834664de.tar.zst coredns-5a4e4d92eff368a552fb01dd5a2874d3834664de.zip | |
Doc tweaks (#2763)
* fix date on 150 release notes
* fix syntax in route53 plugin
Signed-off-by: Miek Gieben <miek@miek.nl>
| -rw-r--r-- | notes/coredns-1.5.0.md | 2 | ||||
| -rw-r--r-- | plugin/route53/README.md | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/notes/coredns-1.5.0.md b/notes/coredns-1.5.0.md index d1e55a64b..803035007 100644 --- a/notes/coredns-1.5.0.md +++ b/notes/coredns-1.5.0.md @@ -3,7 +3,7 @@ title = "CoreDNS-1.5.0 Release" description = "CoreDNS-1.5.0 Release Notes." tags = ["Release", "1.5.0", "Notes"] release = "1.5.0" -date = "2019-04-02T08:01:07+00:01" +date = "2019-04-06T08:24:07+00:01" author = "coredns" +++ diff --git a/plugin/route53/README.md b/plugin/route53/README.md index 2711f2564..3eb27c974 100644 --- a/plugin/route53/README.md +++ b/plugin/route53/README.md @@ -26,10 +26,10 @@ 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. -* **HOSTED*ZONE*ID** the ID of the hosted zone that contains the resource record sets to be +* **HOSTED_ZONE_ID** the ID of the hosted zone that contains the resource record sets to be accessed. -* **AWS*ACCESS*KEY_ID** and **AWS*SECRET*ACCESS_KEY** the AWS access key ID and secret access key +* **AWS_ACCESS_KEY_ID** and **AWS_SECRET_ACCESS_KEY** 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. |