Facebook appears to be down this morning due to what appears to be DNS resolution problems. Many DNS servers do not return any answer for www.facebook.com. Some appear to return but they may have just cached the name. Telneting port 80 of 126.96.36.199 (one of the IPs to which www.facebook.com resolves) connects successfully to the facebook webserver:
x.local: telnet 188.8.131.52 80
Connected to www-11-06-prn1.facebook.com.
Escape character is ‘^]’.
GET / HTTP/1.1
HTTP/1.1 302 Found
Content-Type: text/html; charset=utf-8
Date: Wed, 07 Mar 2012 06:37:09 GMT
A DNS query to one of the the facebook DNS servers (glb1.facebook.com [184.108.40.206]
glb2.facebook.com [220.127.116.11]) fails as below:
> server 18.104.22.168
Default server: 22.214.171.124
;; connection timed out; no servers could be reached
I got successful DNS queries from here. Twitter is catching fire with “facebook down” reports from Southern Europe and elsewhere at this moment. Are we set for a highly productive day around the globe or for severe withdrawal symptoms… 🙂
PS: It gets weirder. Reverse lookup on one of the IPs of www.facebook.com resolves properly while www.facebook.com does not:
Server: 10.1.1.1 Address: 10.1.1.1#53
126.96.36.199.in-addr.arpa name = www-12-02-ash3.facebook.com.
Authoritative answers can be found from: 242.171.69.in-addr.arpa
nameserver = ns5.facebook.com. 242.171.69.in-addr.arpa
nameserver = ns4.facebook.com. 242.171.69.in-addr.arpa
nameserver = ns3.facebook.com. ns3.facebook.com
internet address = 188.8.131.52 ns4.facebook.com
internet address = 184.108.40.206 ns5.facebook.com
internet address = 220.127.116.11
;; Truncated, retrying in TCP mode. ;; Connection to 10.1.1.1#53(10.1.1.1) for www.facebook.com failed: connection refused.