Here's some. Check the AAAA for:
I meant, check the literal IPv6 addresses that correspond to these hostnames. I'll put emphasis so it is more visible :)
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.
PING sprint.net: 56 data bytes
64 bytes from www.sprint.net (2600::): icmp_seq=0. time=156. ms
64 bytes from www.sprint.net (2600::): icmp_seq=1. time=151. ms
64 bytes from www.sprint.net (2600::): icmp_seq=2. time=153. ms
64 bytes from www.sprint.net (2600::): icmp_seq=3. time=151. ms
64 bytes from www.sprint.net (2600::): icmp_seq=4. time=151. ms
----sprint.net PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms) min/avg/max/stddev = 151./152./156./2.5
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.
I'll think about it. For now afraid.org just works.
my site jcs.org has been dual-homed for quite a while.
[~] 0 (jon@snowball2)
$ ping itchy.jrock.us
PING itchy.jrock.us (126.96.36.199) 56(84) bytes of data.
64 bytes from itchy.jrock.us (188.8.131.52): icmp_req=1 ttl=49 time=59.4 ms
[~] 0 (jon@snowball2)
$ ping6 itchy.jrock.us
PING itchy.jrock.us(2600:3c00::f03c:91ff:fe93:50b0) 56 data bytes
64 bytes from 2600:3c00::f03c:91ff:fe93:50b0: icmp_seq=1 ttl=246 time=36.6 ms
But it's a mixed bag. All one can conclusively say that the average patient temperature in the hospital is pretty close to normal.
Anyone have any theories? Ideas?
(Make sure you read the comments for clarifications and fixes)
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.
Anyway, I'm trying to get everyone to test IPv6, and believe me most people are not going to want to set up a tunnel to do this.
Edit: and the "point" of today is to test IPv6 in software. Only a tiny part is to make sure that IPv6 can be routed across the internet-at-large.
Though you can as well use the 2001:db8::/32 and later you can also publish your examples readily.
My comment was about any testing that involves the boxes that may want IPv4 or IPv6 connectivity to external world, apologies if I misunderstood.
Sites that already had IPv4 records work.
$ 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
email@example.com [~]# host jacen.kly.no
jacen.kly.no has IPv6 address 2001:16d8:eea2:30::dead
firstname.lastname@example.org [~]# host civ5.flexd.net
civ5.flexd.net has address 184.108.40.206
civ5.flexd.net has IPv6 address 2001:16d8:eea2:30::beef
email@example.com [~]# 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!
Coincidence I'm sure.
When can we start an annual "turn off ipv4" day? http://bgp.he.net/ipv6-progress-report.cgi suggests that we'll have to wait a while.
Edit: Actually, I think SANS just linked to the wrong site. It should be http://www.worldipv6day.org/
The bbc is odd, as www.bbc.co.uk has ipv6 address 2001:4b10:bbc::2 but Firefox only connects to ipv4..  finally connected on ipv6 after a restart...
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
checked with ipv6 check @ http://www.upordown.de/www.youtube.com
Either my gmail or work address could work as XMPP contact.
I just did mine; I got a new IPv6 address and the same IPv4 address.
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).