Facebook over IPv6
nanog at 85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org
Sat Jun 11 03:20:40 CEST 2011
On Fri, 10 Jun 2011 15:47:25 -0700
Ted Mittelstaedt <tedm at ipinc.net> wrote:
> On 6/10/2011 6:19 AM, Bill Owens wrote:
> > On Thu, Jun 09, 2011 at 09:43:00PM -0700, Ted Mittelstaedt wrote:
> >> We never raised a finger to get on the "Google whitelist" but we
> >> have no trouble accessing Google via IPv6. And we have our own
> >> ARIN-assigned IPv6 block.
> >> IMHO the whole concept of whitelisting IPv6 blocks is ridiculous.
> > Perhaps, but that's not how the Google DNS whitelist works:
> > http://www.google.com/intl/en/ipv6/
> > The important question is this: what caching resolver do you use to
> > query for google.com names? That's what determines whether you're in
> > the whitelist or not.
> > Bill.
> OK I looked at that, the issue is I was hitting ipv6.google.com not
> www.google.com. I guess they are only blacklisting you if you
> attempt to pull AAAA records for www.google.com
> Very likely I will never request to be on the whitelist, because
> of the Google stipulation:
> •Separate DNS servers for your IPv6 users (not shared with IPv4-only users)
> which is, IMHO, asinine. We pay a damn lot of money for our telco space
> and I'm not going to waste 2U plus electricity on 2 machines to loaf
> around answering the occasional IPv6 DNS query when we already have
> perfectly good DNS servers.
> What the hell is wrong with these assholes? Who the hell do they think
> they are?
More information about the ipv6-ops