mirror of
https://github.com/coredns/coredns.git
synced 2025-11-01 10:43:17 -04:00
f3134da45e
* Clean up tests logging This cleans up the travis logs so you can see the failures better. Older tests in tests/ would call log.SetOutput(ioutil.Discard) in a haphazard way. This add log.Discard and put an `init` function in each package's dir (no way to do this globally). The cleanup in tests/ is clear. All plugins also got this init function to have some uniformity and kill any (future) logging there in the tests as well. There is a one-off in pkg/healthcheck because that does log. Signed-off-by: Miek Gieben <miek@miek.nl> * bring back original log_test.go Signed-off-by: Miek Gieben <miek@miek.nl> * suppress logging here as well Signed-off-by: Miek Gieben <miek@miek.nl>
route53
Name
route53 - enables serving zone data from AWS route53.
Description
The route53 plugin is useful for serving zones from resource record sets in AWS route53. This plugin only supports A and AAAA records. The route53 plugin can be used when coredns is deployed on AWS.
Syntax
route53 [ZONE:HOSTED_ZONE_ID...] {
[aws_access_key AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY]
}
- ZONE the name of the domain to be accessed.
- 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 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.
Examples
Enable route53, with implicit aws credentials:
. {
route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7
}
Enable route53, with explicit aws credentials:
. {
route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7 {
aws_access_key AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY
}
}