Sorry about this. When asked for the right thing it does resolv! $ dig aaaa www.facebook.com ;; QUESTION SECTION: ;www.facebook.com. IN AAAA ;; ANSWER SECTION: www.facebook.com. 30 IN AAAA 2620:0:1c08:4000:face:b00c:0:3

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.

On Tue, Jun 7, 2011 at 5:04 PM, fredrik danerklint

<fredan-nanog@fredan.se>wrote:

...

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.

-- //fredan

-- //fredan