Untitled attachment

Notices where this attachment appears

1. Embed this notice
   John Kristoff (jtk@infosec.exchange)'s status on Friday, 03-Jan-2025 17:59:11 JST John Kristoff

   in reply to

   @sahil No. The NS RRset for aws.amazon.com (at this writing and from my vantage point) is:

   ns-106.awsdns-13.com.
   ns-1402.awsdns-47.org.
   ns-1860.awsdns-40.co.uk.
   ns-905.awsdns-49.net.

   That happens to be the same set for tp.8e49140c2-frontier.amazon.com, which is where your dig ns aws.amazon.com query would have stopped.

   aws.amazon.com and tp.8e49140c2-frontier.amazon.com. both happen to be CNAMEs that ultimately lead to dr49lng3n1n2s.cloudfront.net. Those three strung together make up a chain. All coincidentally have the same authoritative server set at present.

   You say "actual NS domain". It might help to further explain if you say what you think the "domain" is in this case.

2. Embed this notice
   sahilister (sahil@toots.sahilister.in)'s status on Thursday, 02-Jan-2025 19:32:59 JST sahilister

   Okay a DNS question, while checking name server for aws.amazon.com, I get:

   ```
   aws.amazon.com. 4092 IN CNAME tp.8e49140c2-frontier.amazon.com.
   tp.8e49140c2-frontier.amazon.com. 46 IN CNAME dr49lng3n1n2s.cloudfront.net.
   dr49lng3n1n2s.cloudfront.net. 12 IN A 108.158.61.79
   ...

   ```

   If I understand correctly, NS for aws.amazon.com is a chain of CNAME(s) to actual NS domain?

   #dns #amazon #aws