facebook lost their A-record for www.facebook.com?

[igor@vds ~]$ host -t A www.facebook.com ns1.facebook.com
Using domain server:
Name: ns1.facebook.com
Address: 204.74.66.132#53
Aliases:

www.facebook.com has no A record

However:

[igor@vds ~]$ dig A www.facebook.com @ns1.facebook.com

; <<>> DiG 9.7.0-P2-RedHat-9.7.0-5.P2.el6_0.1 <<>> A www.facebook.com
@ns1.facebook.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55657
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;www.facebook.com. IN A

;; AUTHORITY SECTION:
www.facebook.com. 86400 IN NS glb2.facebook.com.
www.facebook.com. 86400 IN NS glb1.facebook.com.

;; ADDITIONAL SECTION:
glb2.facebook.com. 3600 IN A 69.171.255.10
glb1.facebook.com. 3600 IN A 69.171.239.10

;; Query time: 11 msec
;; SERVER: 204.74.66.132#53(204.74.66.132)
;; WHEN: Wed Mar 7 08:42:44 2012
;; MSG SIZE rcvd: 104

Not sure what is going wrong here. People @ facebook?

regards, Igor

No, it's a subdomain with its A records in another server.

$ host -t A www.facebook.com glb1.facebook.com.
Using domain server:
Name: glb1.facebook.com.
Address: 69.171.239.10#53
Aliases:

www.facebook.com has address 69.171.224.12

Try dig +trace www.facebook.com to see why.

We also picked up problems with www.facebook.com from our monitoring systems. Starting from 04:00 UTC there were some latency spikes and then from 06:15 UTC thru 07:55 UTC the site was unreachable.

www.v6.facebook.com had no issues though :wink:

Good point Octavio . +trace with dig is always useful when getting weird
results.

Anurag Bhatia
http://anuragbhatia.com

They had issues in Europe today:
http://www.telegraph.co.uk/technology/facebook/9128716/Facebook-hit-by-two-h
our-blackout.html
http://www.washingtonpost.com/business/technology/facebook-back-up-after-eur
ope-outage/2012/03/07/gIQAJnNuwR_story.html

Frank