World IPv6 day(server1.test-ipv6.com)
server1.test-ipv6.com
World IPv6 day
http://server1.test-ipv6.com/ipv6day.html
17 comments
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 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.
There's a good reason test-ipv6.com doesn't have an IPv6 address. If your IPv6 is broken then you can't go to that site to test it :).
That makes no sense at all to me.
If your IPv6 is working you can't go to the site to test it unless you also have working IPv4.
There is absolutely no reason why test-ipv6.com can't have both an A record and an AAAA record.
If your IPv6 is working you can't go to the site to test it unless you also have working IPv4.
There is absolutely no reason why test-ipv6.com can't have both an A record and an AAAA record.
Per the FAQ:
Q: Why is this web site reachable via IPv4 only?
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..
Q: Why is this web site reachable via IPv4 only?
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..
I stand corrected. That makes sense (even if it is frustrating).
facebook has ipv6, on wwww.v6.facebook.com
www.v6.facebook.com. 3600 IN AAAA 2620:0:1cfe:face:b00c::3
Maybe on ipv6 day they might put that on the main www.facebook.com name too - no idea.
www.v6.facebook.com. 3600 IN AAAA 2620:0:1cfe:face:b00c::3
Maybe on ipv6 day they might put that on the main www.facebook.com name too - no idea.
Would a public proxy that has IPv4 and 6 at the same time help?
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.
http://cacm.acm.org/magazines/2011/4/106582-successful-strat...
"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.
http://cacm.acm.org/magazines/2011/4/106582-successful-strat...
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).
Examples of sites that get positive results would be:
http://ready.chair6.net/?url=arin.net
http://ready.chair6.net/?url=he.net
Examples of not-so-ready results: http://ready.chair6.net/?url=news.ycombinator.com http://ready.chair6.net/?url=facebook.com
(Granted, some of these tests are not relevant - say, where all you want to do is provide AAAA records for your web site.)
Examples of not-so-ready results: http://ready.chair6.net/?url=news.ycombinator.com http://ready.chair6.net/?url=facebook.com
(Granted, some of these tests are not relevant - say, where all you want to do is provide AAAA records for your web site.)
Can someone from hn write up a post outlining what we as individuals and web entrepreneurs need to do in order to adapt to ipv6? Thanks
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.