(no title)
danielhunt | 9 years ago
That doesn't apply here though. Instances that are already up are experiencing DNS resolution issues because the Amazon-provided DNS service (which is distinct from Route53) is failing
danielhunt | 9 years ago
That doesn't apply here though. Instances that are already up are experiencing DNS resolution issues because the Amazon-provided DNS service (which is distinct from Route53) is failing
aidos|9 years ago
What you see as zone A is not what I see as zone A (maybe). When you sign up for an account, AWS assigns your zone A to one of the 3 available zones:
That's why people see different outage characteristics between the zones.Edit: one of the few articles (other than HN comments) that explains it https://alestic.com/2009/07/ec2-availability-zones/
danielhunt|9 years ago
All I can say is "WHAAAAAAT?!"
You've made me question my reality. Take an upvote for that alone.