mirror of
https://github.com/coredns/coredns.git
synced 2025-10-27 00:04:15 -04:00
ba1efee4f1
Every plugin needs to deal with EDNS0 and should call Scrub to make a message fit the client's buffer. Move this functionality into the server and wrapping the ResponseWriter into a ScrubWriter that handles these bits for us. Result: Less code and faster, because multiple chained plugins could all be calling scrub and SizeAndDo - now there is just one place. Most tests in file/* and dnssec/* needed adjusting because in those unit tests you don't see OPT RRs anymore. The DNSSEC signer was also looking at the returned OPT RR to see if it needed to sign - as those are now added by the server (and thus later), this needed to change slightly. Scrub itself still exist (for backward compat reasons), but has been made a noop. Scrub has been renamed to scrub as it should not be used by external plugins. Fixes: #2010 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
}
}