On 6/8/12 1:19 AM, Joly MacFie wrote:
Netflix may have created its own IPv6-specific domain which is responsible for almost a third of all IPv6 traffic. If this is the case it might not be in full compliance with the spirit of World IPv6 Day, as the aim should have been for Netflix to operate one single domain with both AAAA records for IPv6 and A records for IPv4.
What about that?
I've asked Sandvine to explain exactly what this means. We haven't created anything IPv6 specific, aside from starting to serve 100% of our IPv6 traffic from the Netflix CDN instead of our CDN partners, which is irrelevant to this actual exercise.
j
On 6/7/12 10:23 PM, Daniel Roesen wrote:
On Fri, Jun 08, 2012 at 12:11:20PM +1000, Mark Andrews wrote:
$ dig @pdns3.ultradns.org <http://pdns3.ultradns.org>
www.netflix.com <http://www.netflix.com>. A +norec +short
wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com <http://wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com>. $ dig @pdns3.ultradns.org <http://pdns3.ultradns.org> www.netflix.com <http://www.netflix.com>. AAAA +norec +short
dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com <http://dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com>.
$ dig @pdns3.ultradns.org <http://pdns3.ultradns.org> www.netflix.com <http://www.netflix.com>. ANY +short +norec $
Resolving www.netflix.com <http://www.netflix.com> using ANY RRtype fails with an empty answer section in the DNS response.
Which is just plain BROKEN.
Yup.
This DNS trickery seems to be from the "taking a shower, trying not to get wet" department. And has adverse effects in corner cases. While playing around, I had periods of time where I couldn't resolve
On Fri, Jun 8, 2012 at 12:31 AM, David Temkin <dave@temk.in <mailto:dave@temk.in>> wrote: the FQDN
at all, possibly due some caching of the empty response.
It's not DNS trickery.
The "trickery" is returning different CNAMEs for QTYPE=A and QTYPE=AAAA. I'm not sure what's the goal of that is, but it's 4am here so I have an excuse of not seeing the light. :)
Best regards, Daniel
We've confirmed that UltraDNS had "additional" issues caused by the push that they fixed for the previously reported problem. We are actively engaged with them to come to a resolution.
-Dave
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast WWWhatsup NYC - http://wwwhatsup.com http://pinstand.com - http://punkcast.com VP (Admin) - ISOC-NY - http://isoc-ny.org -------------------------------------------------------------- -