And while you're at it - maybe enable AAAA record for your site and give it a whirl! (and come up with some more creative IPv6 addresses in the process!) Thanks to guylhem for reminding about this.
I use dead:beef and feed:cafe for my 2 small subnets on a /48 I got from he.net, because it's easy to remember.
Of course, if you really want to identify your allocation, setup reverse dns. To do it the easy way go to afraid.org. They offer a great free service, IMHO better than dyndns.
My web site has been open for ipv6 business for a while. At home today, I installed tunneling software on my openwrt box, and it's working with comcast. Once I found the right set of instructions it went smoothly (https://wiki.xkyle.com/Comcast_IPv6_on_Openwrt). I can see unicorns now: http://ismyipv6working.com/
Interesting how South America and Africa have absolutely zero traffic reported. I thought at least Africa, with it's shortage of IPv4 addresses, much like Asia, would have picked up on IPv6 to a larger extent than the "IPv4 wealthy" nations in the industrialized parts of the world.
99.99% of people won't have an IPv6 connection and can't be bothered to set up a tunnel. However it's still possible to play with IPv6 on your home network, and relatively simple too if you have at least one Linux box:
The point of the day is to ensure that enabling AAAAs on the server side does not break the world. clientside IPv6 connectivity is a nice plus, but optional.
A couple of corrections:
1) ULAs are normally not routable over the internet. Though of course blocking them explicitly would not hurt.
2) depending on the RFC3484 configuration on the hosts, this "IPv6" might break connectivity to dualstack sites.
Please - go to tunnelbroker.net (or sixxs.net) and get yourself a tunnel - it is not that difficult, really.
The large company I work for (~5000 people worldwide) doesn't appear to support any of this. Attempting to reach ipv6day.org gives the message "No DNS records."
I have fully working IPv6 connectivity (10/10 by test-ipv6.com metrics), but ipv6day.org still fails for me. It seems that the problem is that there're no A/AAAA records:
$ host -t AAAA ipv6day.org
ipv6day.org has no AAAA record
$ host -t A ipv6day.org
ipv6day.org has no A record
$ host -t MX ipv6day.org
ipv6day.org mail is handled by 20 mail2.consulintel.es.
ipv6day.org mail is handled by 30 dns1.consulintel.com.
ipv6day.org mail is handled by 10 mail.consulintel.es.
$ host -t SOA ipv6day.org
ipv6day.org has SOA record ns1.euro6ix.com. dnsadmin.consulintel.es. 2010120100 86400 7200 2592000 172800
flexd@flexd.net [~]# host jacen.kly.no
jacen.kly.no has IPv6 address 2001:16d8:eea2:30::dead
flexd@flexd.net [~]# host civ5.flexd.net
civ5.flexd.net has address 178.255.146.39
civ5.flexd.net has IPv6 address 2001:16d8:eea2:30::beef
flexd@flexd.net [~]# host caedus.kly.no
caedus.kly.no has IPv6 address 2001:16d8:eea2:30::daad
IPv4 users hit a IPv4 varnish which redirects to another varnish on the proper server (woo, double). IPv6 hits the proper server varnish directly. Seems to work great from everywhere!
Would be very interesting to hear what the HN folks' experiences are with the whole v6day thing. Hopefully it should be a non-event, but interesting to know anything otherwise.
Comcast came by and ripped the cable off the pole at just about midnight exactly. I've had no internet connection since and have no idea if it'll be back on before the day is over. I'm on HN through my phone.
It's just a good opportunity to configure services and test how it works. Personally I had never touched anything ipv6 related before this spring. There was no real reason to (blame me). Now seems a good moment.
I think that's exactly the idea. If an annual nudge gets some folks to set up ipv6, then there is a steady increase in the size of the ipv6 network. For the most part, no one will have any reason to turn it off again the next day.
Ok, so I was reading about that in the FAQs, that website owners are supposed to turn off IPv6 after today in order to measure the "impact". Not sure what they mean by that.
Before IPv6 day the majors were afraid to enable v6 and accidentally break 1% of their users (somehow). Hopefully once the day is past and the world didn't end, everyone will be comfortable rolling out v6 whenever they want.
Can anyone tell me why http://ipv6day.org is failing after a lengthy timeout, but http://www.ipv6day.org works? There are links to the non-www version in this article, so I assume it worked at some point.
The bbc is odd, as www.bbc.co.uk has ipv6 address 2001:4b10:bbc::2 but Firefox only connects to ipv4.. [edit] finally connected on ipv6 after a restart...
from what i remember, that add-on just tries to resolve hostnames that it sees, it doesn't actually show you whether you connected to that specific ipv4 or ipv6 address.
www.google.com has aaaa 2a00:1450:4008:c00::69
www.youtube.com has aaaa 2a00:1450:4008:c00::be
www.facebook.com has aaaa 2620::1c00:0:face:b00c:0:1
www.bcc.com has aaaa 2001:4b10:bbc::1
Resolving AAAA records doesn't have much to do with IPv6 connectivity. The whole point today is to see what happens when clients receive AAAA records in addition to A records. If a misconfigured client thinks it can use IPv6 but can't, then the existence of that AAAA causes problems.
That's true.
But i think it's real good that these big sites add aaaa records for today. Hopefully the results will show that the percentage of broken users is really small.
Someone has to start deploying ipv6 - either isps or content providers.
There is a button in the dashboard. A script of theirs will alter your MAC address and reboot your machine. When it comes back up, IPv6 is working like a champ.
I just did mine; I got a new IPv6 address and the same IPv4 address.
Well, there went my excuse. I tried to set up a tunnel the other day and couldn't get it to work, but this worked like a champ. I can proudly say my client now owns two of the few IPv6-enabled porn sites on the planet.
CloudFlare handled the DNS like a champ (although I did have to disable and re-enable acceleration for one of the domains to get it to work).
Here's some. Check the AAAA for:
www.facebook.com www.luns.net.uk www.cisco.com
EDIT:
I meant, check the literal IPv6 addresses that correspond to these hostnames. I'll put emphasis so it is more visible :)
2620:0:1c08:4000:===face:b00c===:0:1, 2a01:8900:0:1::===b00b:1e5===, 2001:420:80:1:===c:15c0:d06:f00d===
EDIT2:
And while you're at it - maybe enable AAAA record for your site and give it a whirl! (and come up with some more creative IPv6 addresses in the process!) Thanks to guylhem for reminding about this.