john at sackheads.org
Thu May 21 11:56:11 CDT 2009
On May 21, 2009, at 12:03 PM, Patrick Darden wrote:
> Whois query gets us:
> NS2.FACEBOOK.COM 126.96.36.199
> DNS05.SF2P.TFBNW.NET DNS04.SF2P.TFBNW.NET
> NS1.FACEBOOK.COM 188.8.131.52
> both 184.108.40.206 and 220.127.116.11 are pingable, but DNS queries
> on them directly get various answers:
> nslookup www.facebook.com 18.104.22.168
> *** Can't find www.facebook.com: No answer
> nslookup www.harvard.edu 22.214.171.124
> ** 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?
> Darden, Patrick S. wrote:
>> I noticed this as well around 11:50 eastern.
>> --Patrick Darden
>> -----Original Message-----
>> From: Maria Iano [mailto:maria at iano.org] Sent: Thursday, May 21,
>> 2009 11:56 AM
>> To: nanog at 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.
More information about the NANOG