Commit 5a4e4d92 authored by Miek Gieben's avatar Miek Gieben Committed by GitHub

Doc tweaks (#2763)

* fix date on 150 release notes
* fix syntax in route53 plugin
Signed-off-by: default avatarMiek Gieben <miek@miek.nl>
parent f8aa208c
...@@ -3,7 +3,7 @@ title = "CoreDNS-1.5.0 Release" ...@@ -3,7 +3,7 @@ title = "CoreDNS-1.5.0 Release"
description = "CoreDNS-1.5.0 Release Notes." description = "CoreDNS-1.5.0 Release Notes."
tags = ["Release", "1.5.0", "Notes"] tags = ["Release", "1.5.0", "Notes"]
release = "1.5.0" release = "1.5.0"
date = "2019-04-02T08:01:07+00:01" date = "2019-04-06T08:24:07+00:01"
author = "coredns" author = "coredns"
+++ +++
......
...@@ -26,10 +26,10 @@ route53 [ZONE:HOSTED_ZONE_ID...] { ...@@ -26,10 +26,10 @@ route53 [ZONE:HOSTED_ZONE_ID...] {
domains (private vs. public hosted zone), CoreDNS does the lookup in the given order here. 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. 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. 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 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, AWS credentials the same way as AWS CLI, e.g., environmental variables, AWS credentials file,
instance profile credentials, etc. instance profile credentials, etc.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment