On April 30, 2014 9:30:50 PM CDT, [email protected] wrote: >I'd be interested. > Noted!
>I thought most CDNs went via the local ASN... if tunneled, though, it >probably messes with a lot of such things. > Depends on the CDN, though my limited exposure to them imply reference locality tends toward relation to originating route not by geography. >Google DNS also seems to prefer AAAA records over v4, even, in my >experience. (that was odd troubleshooting) > Yeah, I'd like to hear about your experience (off thread) as the statement is a bit odd and missing some context. Decision is up to the client, when you do a host lookup for an A record you don't get a AAAA... if you do an ANY lookup you'll get A, AAAA etc. If the client is Google (say a crawler) then yeah a dual stacked host tends to prefer v6 over v4 and if you have a published AAAA then that behavior is expected and normal. I would like to know of or find examples of systems that can be configured to prefer a specific address family but so far my experience is has shown it isn't configurable. I'm sure there is a specific RFC to describe the behavior but... lazy. :) If you are referring to Google's recursive resolvers... that's a super interesting question given how they've implemented their v4 & v6 anycast for those now rather famous resolvers. -- Sean _______________________________________________ SkullSpace Discuss Mailing List Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss Archive: https://groups.google.com/group/skullspace-discuss-archive/
