[dns-operations] aws.amazon.com zone has only one nameserver

Nico CARTRON nicolas at ncartron.org
Tue Dec 8 12:48:43 UTC 2015


Hi Yonghua,
On 8 December 2015 at 13:16:40, Yonghua Peng (pyh at cloud-china.org) wrote:

Hi, 

As you see, 

~$ idig aws.amazon.com ns 
aws.amazon.com. 587 IN NS ns-911.amazon.com. 

~$ idig aws.amazon.com soa 
aws.amazon.com. 60 IN SOA ns-911.amazon.com. 
root.amazon.com. 1449536989 3600 900 7776000 60 

~$ idig ns-911.amazon.com 
ns-911.amazon.com. 197 IN A 207.171.178.6 
I’ve got different results, probably due to Amazon using anycast:

;; QUESTION SECTION:

;aws.amazon.com.			IN	NS

;; ANSWER SECTION:

aws.amazon.com.		446	IN	NS	ec2-52-19-138-45.eu-west-1.compute.amazonaws.com.



and



;; QUESTION SECTION:

;aws.amazon.com.			IN	SOA

;; ANSWER SECTION:

aws.amazon.com.		60	IN	SOA	ec2-52-19-138-45.eu-west-1.compute.amazonaws.com. root.amazon.com. 1449578784 3600 900 7776000 60



Do you know why this well known domain has only one nameserver, and it 
seems the nameserver has only one IP? 


Again, Amazon using Anycast, that does not mean everyone is going to the same name server,

but that’s nevertheless weird.



Cheers,

-- 

Nico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dns-oarc.net/pipermail/dns-operations/attachments/20151208/954a7c4d/attachment.html>


More information about the dns-operations mailing list