[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AAAA's for www.netflix.com
- Subject: AAAA's for www.netflix.com
- From: dr at cluenet.de (Daniel Roesen)
- Date: Fri, 8 Jun 2012 03:19:10 +0200
- In-reply-to: <CAFJiuFq6x6+ioZkeTYNWinqXN9EDS7d=4HReLsH9X0R2bnJxjA@mail.gmail.com>
- References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <CAM9VJk24gSmUvHEUVvhfCc1B=8gLev3OZ0F7LE8ivCtwwzAwDw@mail.gmail.com> <CAFJiuFq6x6+ioZkeTYNWinqXN9EDS7d=4HReLsH9X0R2bnJxjA@mail.gmail.com>
On Thu, Jun 07, 2012 at 04:43:41PM -0700, David Temkin wrote:
> What do you mean? www.netflix.com is dual stacked, which represents
> availability of our website (and PC/Mac streaming clients) to100% of our
> users who have IPv6.
The zero TTL on the CNAME an AAAA RRs makes www.netflix.com
zero-stacked at least for some resolvers:
$ dig @pdns3.ultradns.org www.netflix.com. A +norec +short
wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com.
$ dig @pdns3.ultradns.org www.netflix.com. AAAA +norec +short
dualstack.wwwservice--frontend-313423742.us-east-1.elb.amazonaws.com.
$ dig @pdns3.ultradns.org www.netflix.com. ANY +short +norec
$
Resolving www.netflix.com using ANY RRtype fails with an empty answer
section in the DNS response.
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 the FQDN
at all, possibly due some caching of the empty response.
Best regards,
Daniel
--
CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0