4 ms·
AWS says "We are investigating elevated errors resolving the DNS hostnames used to access some AWS services in the US-EAST-1 Region." Is that coincidental, or a
by ljosa 10y ago
AWS says "We are investigating elevated errors resolving the DNS hostnames used to access some AWS services in the US-EAST-1 Region." Is that coincidental, or are they being DDoSed also?
- jpdlla 10y agoHave some errors logged on our side of problems resolving DNS hostname for SES email-smtp.us-east-1.amazonaws.com
- cyberferret 10y agoThat might explain why we are down - most of our EC2 instances are in us-east-1. Looks like Amazon SQS is impacted too. We are getting a stream of undeliverable messages, and our 'dead letter' queue is filling up!
- colanderman 10y agoApparently us-east-1 is backed by Dyn (and only Dyn) as well? $ host -t NS us-east-1.amazonaws.com us-east-1.amazonaws.com name server ns3.p31.dynect.net. us-east-1.amazonaws.com name server ns1.p31.dynect.net. us-east-1.amazonaws.com name server ns2.p31.dynect.net. us-east-1.amazonaws.com name server ns4.p31.dynect.net. That's… utterly bizarre to me. us-east-2 has a more diverse selection: $ host -t NS us-east-2.amazonaws.com us-east-2.amazonaws.com name server u4.amazonaws.com. us-east-2.amazonaws.com name server u6.amazonaws.com. us-east-2.amazonaws.com name server u3.amazonaws.com. us-east-2.amazonaws.com name server u2.amazonaws.com. us-east-2.amazonaws.com name server u1.amazonaws.com. us-east-2.amazonaws.com name server u5.amazonaws.com. us-east-2.amazonaws.com name server ns2.p31.dynect.net. us-east-2.amazonaws.com name server ns1.p31.dynect.net. us-east-2.amazonaws.com name server pdns1.ultradns.net. us-east-2.amazonaws.com name server pdns5.ultradns.info. us-east-2.amazonaws.com name server ns3.p31.dynect.net. us-east-2.amazonaws.com name server ns4.p31.dynect.net. us-east-2.amazonaws.com name server pdns3.ultradns.org. Not that anyone should be running a service whose availability they care about solely in us-east-1 anyway…
- marcoslater 10y agoSame exact thing with EU-WEST-1/2. $ dig ns eu-west-1.amazonaws.com +short ns3.p31.dynect.net. ns1.p31.dynect.net. ns4.p31.dynect.net. ns2.p31.dynect.net. $ dig ns eu-west-2.amazonaws.com +short u6.amazonaws.com. u5.amazonaws.com. u2.amazonaws.com. u4.amazonaws.com. u1.amazonaws.com. u3.amazonaws.com. pdns1.ultradns.net. pdns3.ultradns.org. pdns5.ultradns.info. ns2.p31.dynect.net. ns1.p31.dynect.net. ns4.p31.dynect.net. ns3.p31.dynect.net. I wonder why this is, considering the more extended usage that -1 on each region usually gets. :S
- rdrey 10y agoEx-Amazonian here. I worked on the EC2 API for just over a year, and this could simply be a legacy thing. See https://en.wikipedia.org/wiki/Timeline_of_Amazon_Web_Services https://en.wikipedia.org/wiki/Timeline_of_Amazon_Web_Service.... us-east-1 is the oldest region and predates Route 53. Not adding extra DNS providers to the older regions is probably an oversight. (The EC2 API team requests load balancers from a separate load balancer team. The load balancer team probably didn't exist as a separate team when some of these regions were created.)
- sandinmyjoints 10y agoAWS may have updated this, I now see $ host -t NS us-east-1.amazonaws.com us-east-1.amazonaws.com name server pdns5.ultradns.info. us-east-1.amazonaws.com name server ns3.p31.dynect.net. us-east-1.amazonaws.com name server pdns1.ultradns.net. us-east-1.amazonaws.com name server pdns3.ultradns.org. us-east-1.amazonaws.com name server ns4.p31.dynect.net. us-east-1.amazonaws.com name server ns1.p31.dynect.net. us-east-1.amazonaws.com name server ns2.p31.dynect.net. us-east-1.amazonaws.com name server u1.amazonaws.com. us-east-1.amazonaws.com name server u2.amazonaws.com. us-east-1.amazonaws.com name server u3.amazonaws.com. us-east-1.amazonaws.com name server u4.amazonaws.com. us-east-1.amazonaws.com name server u5.amazonaws.com. us-east-1.amazonaws.com name server u6.amazonaws.com.
- colanderman 10y agoMe too. Someone realized their oopsie :)
- nkozyra 10y agoIf that were the reason I wouldn't expect this update: 6:36 AM PDT [RESOLVED] Between 4:31 AM and 6:10 AM PDT, we experienced errors resolving the DNS hostnames used to access some AWS services in the US-EAST-1 Region. During the issue, customers may have experienced failures indicating "hostname unknown" or "unknown host exception" when attempting to resolve the hostnames for AWS services and EC2 instances. This issue has been resolved and the service is operating normally.