JanB 4d9e4f1487 Make sure we don't provision to a private hosted zone ... Route 53 allows multiple zones with the same name to co-exist in an account. The most common use case for this is a split-view DNS with one private and one public zone for the same domain name. This patch makes sure we don’t ever provision the authorization record to the private zone. The other case where a user has multiple public zones with the same name is not covered here since this would require a bigger change in code in order to determine which of the zones is active from the viewpoint of the internet. Also this is probably an edge use case that can be addressed once it comes up in the issues.		2016-04-21 15:47:43 +02:00
..
fixtures_test.go	Switch route53 provider to the official AWS SDK	2016-03-27 20:22:09 +02:00
route53.go	Make sure we don't provision to a private hosted zone	2016-04-21 15:47:43 +02:00
route53_test.go	Switch route53 provider to the official AWS SDK	2016-03-27 20:22:09 +02:00
testutil_test.go	Switch route53 provider to the official AWS SDK	2016-03-27 20:22:09 +02:00