Hi Folks, To whoever manages DNS for this repository: a more elegant solution not requiring an package patches would have been to follow this practice for DNS on EC2.
Try to use CNAMES to the fully-qualified domain name EC2 instead of A records. For example, at the moment you are using: us-west-1.ec2.archive.ubuntu.com. 600 IN A 10.162.150.127 This address is apparently not routable from the outside world (perhaps to avoid bandwidth charges?) Had you used a routable EC2 Elastic IP, and a CNAME record pointing to the EC2 assigned FQDN, lookup requests by VPC servers would have the public elastic IP returned like this: ;; ANSWER SECTION: us-west-1.ec2.archive.ubuntu.com. 600 IN CNAME ec2-108-20-220-125.compute-1.amazonaws.com. ec2-108-20-220-125.compute-1.amazonaws.com. 300 IN A 108.20.220.125 Lookup requests by VPC servers would have the public elastic IP returned, while instances launched normally in EC2 would receive the private address: ;; ANSWER SECTION: us-west-1.ec2.archive.ubuntu.com. 600 IN CNAME ec2-108-20-220-125.compute-1.amazonaws.com. ec2-108-20-220-125.compute-1.amazonaws.com. 300 IN A 10.252.111.96 I've made these addresses up, of course, and I understand you have multiple servers for each hostname, but we use this method with weighted round robin DNS on EC2 as well and it works as in the example above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/615545 Title: Instances launched in a VPC cannot access ec2.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/615545/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
