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
I noticed this as well around 11:50 eastern.
--Patrick Darden
I don't know that it's a DNS issue. I had trouble reaching facebook.com and www.spc.noaa.gov for a while, as well as a couple IPs in Chicago on residential Comcast. Had issues for about the last half hour but seemingly all is well now. I hope.
-Andy Ringsmuth
Looks like someone is messing with the domain nameservers. Possibly a
domain hijack?
panzer:~ chaynes$ whois facebook.com
Whois Server Version 2.0
Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.
FACEBOOK.COM.ZZZZZ.GET.LAID.AT.WWW.SWINGINGCOMMUNITY.COM
FACEBOOK.COM.ZZZZZ.DOWNLOAD.MOVIE.ONLINE.ZML2.COM
FACEBOOK.COM.MORE.INFO.AT.WWW.BEYONDWHOIS.COM
FACEBOOK.COM
To single out one record, look it up with "xxx", where xxx is one of the
of the records displayed above. If the records are the same, look them
up
with "=xxx" to receive a full display for each record.
- Clay
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.
--p
Darden, Patrick S. wrote:
No, when you do a whois for 'fakebook.com' it will pull any registered NS entries containing facebook.com anywhere in the whois db.
Digging a.gtld-servers.net is the best way to find authoritative NS for facebook.com, not whois.
Clay Haynes wrote:
From Switzerland it is working fine...
1 <1 ms <1 ms <1 ms [10.0.0.1]
2 1 ms <1 ms <1 ms [10.0.0.2]
3 2 ms 1 ms 3 ms 62-2-78-.static.cablecom.ch [62.2.78.]
4 1 ms 1 ms 1 ms 62-2-66-233.static.cablecom.ch [62.2.66.233]
5 * * 1 ms ch-zrh01a-ra1-ge-1-1-0.aorta.net [213.46.171.49]
6 6 ms 6 ms 6 ms ch-gva01a-ra1-ge-0-1-0.aorta.net [213.46.171.9]
7 15 ms 15 ms 15 ms fr-par02a-rd1-ge-15-0-0.aorta.net [213.46.160.49
]
8 96 ms 96 ms 97 ms us-was01a-rd1-pos-2-0.aorta.net [213.46.160.170]
9 97 ms 96 ms 99 ms us-was02a-ri1-ge-0-0-0-0.aorta.net [213.46.190.1
90]
10 99 ms 99 ms 99 ms xe-0.equinix.asbnva01.us.bb.gin.ntt.net [206.223
.115.12]
11 * * * Zeit�berschreitung der Anforderung.
12 97 ms 97 ms 97 ms te-7-4.r05.asbnva01.us.ce.gin.ntt.net [168.143.2
28.34]
13 100 ms 107 ms 108 ms te-10-0.csw06b.ash1.tfbnw.net [204.15.20.155]
14 100 ms 100 ms 100 ms www.11.06.ash1.facebook.com [69.63.186.12]
Ablaufverfolgung beendet.
I think is a Some DNS are false...
Greetings
Xaver
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.132both 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 answerand
nslookup www.harvard.edu 204.74.66.132
** server can't find www.harvard.edu: SERVFAILThis 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?
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