Sorry - my bad - I will post to outages in future. Digs to name servers were showing similar results to Patrick's below. However, it seems to be fixed now. Maria On May 21, 2009, at 12:56 PM, John Payne wrote:
On May 21, 2009, at 12:03 PM, Patrick Darden wrote:
Whois query gets us: NS2.FACEBOOK.COM 204.74.67.132 DNS05.SF2P.TFBNW.NET DNS04.SF2P.TFBNW.NET NS1.FACEBOOK.COM 204.74.66.132
both 204.74.67.132 and 204.74.66.132 are pingable, but DNS queries on them directly get various answers:
nslookup www.facebook.com 204.74.66.132 *** Can't find www.facebook.com: No answer
and nslookup www.harvard.edu 204.74.66.132 ** server can't find www.harvard.edu: SERVFAIL
This tells me the DNS is set up and semi-working, but incorrectly. It answers correctly for a query for a domain outside its purview, but with a "No answer" for stuff it should know.
a) why are you relying on whois for stuff that's authoritative in DNS? b) isn't this what the outages list is for?
--p
Darden, Patrick S. wrote:
I noticed this as well around 11:50 eastern.
--Patrick Darden
-----Original Message----- From: Maria Iano [mailto:maria@iano.org] Sent: Thursday, May 21, 2009 11:56 AM To: nanog@nanog.org Subject: facebook DNS
It looks like facebook is having DNS troubles. The www.facebook.com subdomain is delegated to some servers that are no longer answering. Also apps.facebook.com is a cname to www- college.facebook.com which gets no reply.
Maria