Nobody is ready for IPv6 yet, and it's depressing.
I tried an experiment the other day, turning off IPv4 and using only IPv6 on a desktop at home. HN, Ars Technica, Twitter, Facebook... none of them even have an AAAA record. Google does for the main google.com site and for gmail, but not for Google Talk. Hell, even test-ipv6.com doesn't have an AAAA record.
This is not the expected transition plan to IPv6. You do not turn IPv4 off. During the first phase of the transition period, new users are supposed to run IPv4 and IPv6 side-by-side, so they can reach both parts of the Internet without issues.
You just jumped to the third phase of the transition plan while the rest of the world is busy doing the first one. That ain't gonna work.
You're right, there are no AAAA records, intentionally. A percentage of users are unable to browse sites that are dual-stack. If the users can't connect, then they can't be told they have a problem. This is a big problem facing content providers today; of which, I work at one for my $dayjob. As such, the main test page requires IPv4 (either native or translated).
At some point, when the percentage of "broken" users has gone significantly down, I'll consider making test-ipv6.com dual-stack..
yes, but then it might be easier if you just find a nat64 server and use that. I've run that for time and used an IPv6-only network like that for a few weeks, and it works "ok". Most HTTP stuff works, but things like Skype, FTP, and local DLNA (PS3 streaming) don't work at all.
Great article in Communications of the ACM, with a foreword by Vint Cerf:
"Successful Strategies for IPv6 Rollouts. Really."
The gist is that changing everything at once will probably fail because of how large the task is. Instead, change the web-facing load balancer to offer IPv6 to external customers, while translating to IPv4 for internal communication. That is the fastest way to get started.
We've been double checking bug reports and doing extra testing to make sure that Firefox is ready for World IPv6 day. If you find any problems with Firefox while testing IPv6 (or ever, really) please let us know at "bugzilla.mozilla.org"!
That site seems to focus on client connectivity tests .. http://ready.chair6.net will do some basic server-focused tests (enter a domain/URL to test for IPv6 connectivity).
I tried an experiment the other day, turning off IPv4 and using only IPv6 on a desktop at home. HN, Ars Technica, Twitter, Facebook... none of them even have an AAAA record. Google does for the main google.com site and for gmail, but not for Google Talk. Hell, even test-ipv6.com doesn't have an AAAA record.