3 ms·
Apparently 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.n
by colanderman 10y ago
Apparently 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 :)
- paulddraper 10y ago> Not that anyone should be running a service whose availability they care about solely in us-east-1 anyway Don't confuse regions with availability zones. (Though in this case, the availability zones don't help...)
- colanderman 10y agoOh good point, my bad.