Re: IPv6 readiness and tinydns.

> <snip>
> On 2008-01-12 Russ Nelson wrote:
> 
>    "When Google has an AAAA record, we can talk about adding IPv6 support."
> 
> I think we are ready to start talking:
> 
>    http://www.google.com/intl/en/ipv6/faq.html
> </snip>

Hmm:

[dean@citation2 dean]$ dig +noall +answer any ns1.google.com
ns1.google.com.         345600  IN      A       216.239.32.10
[dean@citation2 dean]$ dig +noall +answer any ns2.google.com
ns2.google.com.         345437  IN      A       216.239.34.10
[dean@citation2 dean]$ dig +noall +answer any ns3.google.com
ns3.google.com.         345600  IN      A       216.239.36.10
[dean@citation2 dean]$ dig +noall +answer any ns4.google.com
ns4.google.com.         345600  IN      A       216.239.38.10
[dean@citation2 dean]$ dig +noall +answer any www.google.com
www.google.com.         496777  IN      CNAME   www.l.google.com.
[dean@citation2 dean]$ dig +noall +answer any www.l.google.com
www.l.google.com.       300     IN      A       72.14.204.99
www.l.google.com.       300     IN      A       72.14.204.103
www.l.google.com.       300     IN      A       72.14.204.104
www.l.google.com.       300     IN      A       72.14.204.147

It's not time yet. But from the FAQ: 

  We enable Google over IPv6 on request for networks where IPv6 access 
  will provide the same or better quality of experience of Google 
  services as IPv4. 

  Our measurements show that enabling Google over IPv6 can result in a 
  small percentage of users experiencing problems or delays accessing 
  Google services. In many cases, we have found this to be due to user 
  network issues such as misconfiguration or equipment that does not 
  properly support IPv6. 

That percentage isn't really that small. Its large enough that they only
turn it on, on request. You might want to consider this before spending
a lot of time on IPV6:

http://www.ietf.org/mail-archive/web/tls/current/msg07143.html

And this message was sent to list, hasn't shown up in archives yet:

====================================================
Date: Mon, 01 Nov 2010 17:57:26 +1300
From: Peter Gutmann <[email protected]>
To: [email protected], [email protected]
Cc: [email protected]
Subject: Re: [TLS] Server Name Indication (SNI) in an IPv6 world?

Dean Anderson <[email protected]> writes:

>That's why now when you google IPV6, you bring up more and more pages on how
>to disable it.

This sounded sufficiently controversial that I had to try it:

Google "ipv6" -> 11m hits.
Google "ipv6"+"disable" -> 0.9m hits.
Google "ipv6"+"turn off" -> 1.8m hits.

So roughly 10-20% of references to IPv6 are on how to disable it.  Wow.

Peter.
====================================================




On Tue, 2 Nov 2010, Russell Sutherland wrote:

> I am attempting to prepare our infrastructure here to be IPv6 ready.
> Part of that is DNS. For several years we have used the fefe.de patch to
> serve up AAAA records for several sub-domains. In the documentation it
> states explicitly that:
> 
>     .... tinydns-edit won't accept IPv6 addresses for NS or MX records yet
> 
> So my short question is, can one use a patched version of tinydns to fulling
> support an IPv6 environment?
> 

-- 
Av8 Internet   Prepared to pay a premium for better service?
www.av8.net         faster, more reliable, better service
617 256 5494