www.juniper.net is on IPv6
www.facebook.com has AAAA but doesn't load for me over IPv6, it does for others though
www.level3.com works fine over v4 but shows a 404 over IPv6
www.simobil.si is temporarily unavailable over IPv6 but works fine over IPv4
If you go to www.v6.facebook.com it works, but it seems they have some problem on their main site. I am seeing some issues reaching them over IPv6.
- Jared
At this second, I don't see the AAAA, though they may only be providing it to v6 dns servers?
Jack
They were serving up 2620:0:1cff:ff01::23 from my universe, but it was not accepting tcp/80 requests. They also may have pulled the trigger a bit earlier than expected..
This may explain the problem if people confused 2300 with 0000 due to daylight savings time or something else.
- Jared
No issues connecting to FB for me on IPv6 (both to www.v6.facebook.com and to the AAAA returned by www.facebook.com now).
Interesting (perhaps) side note - www.facebook.com has a AAAA, but "facebook.com" does not.
Google / Youtube records are up and running nicely also.
J.
And "thefacebook.com"? 
Cheers,
-- jr 'Yes; that's operational. How many obscure aliases do *you* have?' a
yahoo is already serving up the AAAA as well.
Thanks Igor!
Looking forward to seeing the traffic spike today
- Jared
Here I don't see any v6 for either facebook.com or www.facebook.com (I
run my own resolver from within comcast, and the resolver and my boxes
are all v6 enabled and dual-stacked, have been for over a year).
I did see a cute pair of puns in cisco's v6-day address:
cisco.v6day.akadns.net has IPv6 address 2001:420:80:1:c:15c0:d06:f00d
(check the last 32 bits, and the 32 before...)
-- Pete
No issues connecting to FB for me on IPv6 (both to www.v6.facebook.com and to the AAAA returned by www.facebook.com now).
Interesting (perhaps) side note - www.facebook.com has a AAAA, but "facebook.com" does not.
Google / Youtube records are up and running nicely also.
....
Here I don't see any v6 for either facebook.com or www.facebook.com (I
run my own resolver from within comcast, and the resolver and my boxes
are all v6 enabled and dual-stacked, have been for over a year).
Google must be exercising very fine control over their dns; it turned v6
on at 19:58 exactly. Yahoo's is still
not on as seen from here.
www.facebook.com (but not facebook.com) just turned on here too (after
google). another hex-speak spelling...
-- Pete
This is from Sweden.
$ dig any www.facebook.com @ns1.facebook.com
; <<>> DiG 9.7.3 <<>> any www.facebook.com @ns1.facebook.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61742
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;www.facebook.com. IN ANY
;; AUTHORITY SECTION:
www.facebook.com. 86400 IN NS glb1.facebook.com.
www.facebook.com. 86400 IN NS glb2.facebook.com.
;; ADDITIONAL SECTION:
glb1.facebook.com. 3600 IN A 69.171.239.10
glb2.facebook.com. 3600 IN A 69.171.255.10
;; Query time: 58 msec
;; SERVER: 204.74.66.132#53(204.74.66.132)
;; WHEN: Wed Jun 8 02:01:37 2011
;; MSG SIZE rcvd: 104
No AAAA records at the moment. Checked alll their nameservers.
I'm using my iPhone as the IPv6-only canary. www.facebook.com now seems to work, but it redirects to m.facebook.com which doesn't have IPv6. This seems to be a trend, yahoo and cnn do the same thing. Annoying.
I'm getting v6 for facebook now.
-Randy
Same results here, western US.
~Seth
Props to google for doing it right, e.g.:
maps.googleapis.com AAAA
gg.google.com AAAA
safebrowsing.clients.google.com AAAA
Thank you google!
- Jared
That's because you're asking the wrong nameservers. The response you're
getting is pointing you to the correct nameservers (glb1/glb2.facebook.com)
which are defintely returning AAAA records for me :
$ dig +short aaaa www.facebook.com @glb1.facebook.com
2620:0:1c08:4000:face:b00c:0:3
Scott.
Indeed. Verizon LTE is v6 enabled but the user-agent on my phone denies me an IPv6 experience.
My iphone picks up a v6 address from our wireless network but not from
AT&T as far as I can tell.
google actually enabled a v6 address for at least part of their picture
cdn along with the top page. I might try the iphone since it gets
redirected to m.* a lot, though I'd presume (Cameron notwithstanding...)
that very few of the participants are enabling their mobile
infrastructure for v6 yet.
OTOH, see:
%host m.google.com
m.google.com is an alias for mobile.l.google.com.
mobile.l.google.com has address 72.14.204.193
mobile.l.google.com has IPv6 address 2001:4860:800f::c1
So far, looks like Google has done a good job.
I don't know if they are doing any of their geolocation-based dns on the
v6 stuff; my v6 address is from HE at ashburn...
-- Pete
This appears to be normal, but check the authoritative servers it gives.
;; AUTHORITY SECTION:
www.facebook.com. 86400 IN NS glb1.facebook.com.
www.facebook.com. 86400 IN NS glb2.facebook.com.
They respond with AAAA with aa bit set.
www.juniper.net is on IPv6
www.facebook.com has AAAA but doesn't load for me over IPv6, it does for others though
Working great for me. Getting to it via HE.
www.level3.com works fine over v4 but shows a 404 over IPv6
Yes, I am seeing that too. Cute.
michael