facebook.com DNS not found 20120218 2125 UTC
facebook.com DNS not found 20120218 2125 UTC Is there any outage information for DNS for facebook.com / www.facebook.com ? "Oops! Google Chrome could not find www.facebook.com" On Fri, Feb 17, 2012 at 11:26 PM, <nanog-request@nanog.org> wrote:
Send NANOG mailing list submissions to nanog@nanog.org
-- R/ Everett Batey / Skype: wa6cre-10 / efbatey@gmail.com or efbarc@cotdazr.org or wa6cre@rabbitradio.org or lioneverett@gmail.com Lions 4-A3 Calendar / CrisisLinks http://bit.ly/cw95Um Please visit So Calif Linux Expo http://www.socallinuxexpo.org (805) 616-2471 / G-Talk/Twitter: efbatey
On Sat, 18 Feb 2012 13:32:42 -0800 Everett Batey <efbatey@gmail.com> wrote:
facebook.com DNS not found 20120218 2125 UTC Is there any outage information for DNS for facebook.com / www.facebook.com ? "Oops! Google Chrome could not find www.facebook.com"
Not here dig +trace www.facebook.com ; <<>> DiG 9.7.3 <<>> +trace www.facebook.com ;; global options: +cmd . 157853 IN NS d.root-servers.net. . 157853 IN NS j.root-servers.net. . 157853 IN NS c.root-servers.net. . 157853 IN NS f.root-servers.net. . 157853 IN NS b.root-servers.net. . 157853 IN NS l.root-servers.net. . 157853 IN NS h.root-servers.net. . 157853 IN NS m.root-servers.net. . 157853 IN NS a.root-servers.net. . 157853 IN NS k.root-servers.net. . 157853 IN NS g.root-servers.net. . 157853 IN NS e.root-servers.net. . 157853 IN NS i.root-servers.net. ;; Received 228 bytes from 192.168.1.2#53(192.168.1.2) in 3 ms com. 172800 IN NS b.gtld-servers.net. com. 172800 IN NS a.gtld-servers.net. com. 172800 IN NS f.gtld-servers.net. com. 172800 IN NS c.gtld-servers.net. com. 172800 IN NS j.gtld-servers.net. com. 172800 IN NS h.gtld-servers.net. com. 172800 IN NS l.gtld-servers.net. com. 172800 IN NS k.gtld-servers.net. com. 172800 IN NS g.gtld-servers.net. com. 172800 IN NS m.gtld-servers.net. com. 172800 IN NS i.gtld-servers.net. com. 172800 IN NS e.gtld-servers.net. com. 172800 IN NS d.gtld-servers.net. ;; Received 494 bytes from 192.5.5.241#53(f.root-servers.net) in 99 ms facebook.com. 172800 IN NS ns1.facebook.com. facebook.com. 172800 IN NS ns2.facebook.com. facebook.com. 172800 IN NS ns3.facebook.com. facebook.com. 172800 IN NS ns4.facebook.com. facebook.com. 172800 IN NS ns5.facebook.com. ;; Received 204 bytes from 192.33.14.30#53(b.gtld-servers.net) in 208 ms www.facebook.com. 86400 IN NS glb1.facebook.com. www.facebook.com. 86400 IN NS glb2.facebook.com. ;; Received 104 bytes from 66.220.151.20#53(ns3.facebook.com) in 91 ms www.facebook.com. 120 IN A 69.171.234.96 ;; Received 50 bytes from 69.171.255.10#53(glb2.facebook.com) in 20 ms
On Fri, Feb 17, 2012 at 11:26 PM, <nanog-request@nanog.org> wrote:
Send NANOG mailing list submissions to nanog@nanog.org
-- John
Likewise, working here. $ dig +trace www.facebook.com ; <<>> DiG 9.7.0-P1 <<>> +trace www.facebook.com ;; global options: +cmd . 240259 IN NS b.root-servers.net. . 240259 IN NS g.root-servers.net. . 240259 IN NS i.root-servers.net. . 240259 IN NS c.root-servers.net. . 240259 IN NS f.root-servers.net. . 240259 IN NS d.root-servers.net. . 240259 IN NS l.root-servers.net. . 240259 IN NS m.root-servers.net. . 240259 IN NS j.root-servers.net. . 240259 IN NS e.root-servers.net. . 240259 IN NS a.root-servers.net. . 240259 IN NS h.root-servers.net. . 240259 IN NS k.root-servers.net. ;; Received 272 bytes from 192.168.100.1#53(192.168.100.1) in 1 ms com. 172800 IN NS a.gtld-servers.net. com. 172800 IN NS b.gtld-servers.net. com. 172800 IN NS c.gtld-servers.net. com. 172800 IN NS d.gtld-servers.net. com. 172800 IN NS e.gtld-servers.net. com. 172800 IN NS f.gtld-servers.net. com. 172800 IN NS g.gtld-servers.net. com. 172800 IN NS h.gtld-servers.net. com. 172800 IN NS i.gtld-servers.net. com. 172800 IN NS j.gtld-servers.net. com. 172800 IN NS k.gtld-servers.net. com. 172800 IN NS l.gtld-servers.net. com. 172800 IN NS m.gtld-servers.net. ;; Received 494 bytes from 2001:7fd::1#53(k.root-servers.net) in 65 ms facebook.com. 172800 IN NS ns1.facebook.com. facebook.com. 172800 IN NS ns2.facebook.com. facebook.com. 172800 IN NS ns3.facebook.com. facebook.com. 172800 IN NS ns4.facebook.com. facebook.com. 172800 IN NS ns5.facebook.com. ;; Received 204 bytes from 192.48.79.30#53(j.gtld-servers.net) in 361 ms www.facebook.com. 86400 IN NS glb2.facebook.com. www.facebook.com. 86400 IN NS glb1.facebook.com. ;; Received 104 bytes from 66.220.145.65#53(ns5.facebook.com) in 206 ms www.facebook.com. 120 IN A 69.63.190.22 ;; Received 50 bytes from 69.171.255.10#53(glb2.facebook.com) in 146 ms On 02/18/2012 09:39 PM, John Peach wrote:
On Sat, 18 Feb 2012 13:32:42 -0800 Everett Batey <efbatey@gmail.com> wrote:
facebook.com DNS not found 20120218 2125 UTC Is there any outage information for DNS for facebook.com / www.facebook.com ? "Oops! Google Chrome could not find www.facebook.com" Not here
dig +trace www.facebook.com
; <<>> DiG 9.7.3 <<>> +trace www.facebook.com ;; global options: +cmd . 157853 IN NS d.root-servers.net. . 157853 IN NS j.root-servers.net. . 157853 IN NS c.root-servers.net. . 157853 IN NS f.root-servers.net. . 157853 IN NS b.root-servers.net. . 157853 IN NS l.root-servers.net. . 157853 IN NS h.root-servers.net. . 157853 IN NS m.root-servers.net. . 157853 IN NS a.root-servers.net. . 157853 IN NS k.root-servers.net. . 157853 IN NS g.root-servers.net. . 157853 IN NS e.root-servers.net. . 157853 IN NS i.root-servers.net. ;; Received 228 bytes from 192.168.1.2#53(192.168.1.2) in 3 ms
com. 172800 IN NS b.gtld-servers.net. com. 172800 IN NS a.gtld-servers.net. com. 172800 IN NS f.gtld-servers.net. com. 172800 IN NS c.gtld-servers.net. com. 172800 IN NS j.gtld-servers.net. com. 172800 IN NS h.gtld-servers.net. com. 172800 IN NS l.gtld-servers.net. com. 172800 IN NS k.gtld-servers.net. com. 172800 IN NS g.gtld-servers.net. com. 172800 IN NS m.gtld-servers.net. com. 172800 IN NS i.gtld-servers.net. com. 172800 IN NS e.gtld-servers.net. com. 172800 IN NS d.gtld-servers.net. ;; Received 494 bytes from 192.5.5.241#53(f.root-servers.net) in 99 ms
facebook.com. 172800 IN NS ns1.facebook.com. facebook.com. 172800 IN NS ns2.facebook.com. facebook.com. 172800 IN NS ns3.facebook.com. facebook.com. 172800 IN NS ns4.facebook.com. facebook.com. 172800 IN NS ns5.facebook.com. ;; Received 204 bytes from 192.33.14.30#53(b.gtld-servers.net) in 208 ms
www.facebook.com. 86400 IN NS glb1.facebook.com. www.facebook.com. 86400 IN NS glb2.facebook.com. ;; Received 104 bytes from 66.220.151.20#53(ns3.facebook.com) in 91 ms
www.facebook.com. 120 IN A 69.171.234.96 ;; Received 50 bytes from 69.171.255.10#53(glb2.facebook.com) in 20 ms
On Fri, Feb 17, 2012 at 11:26 PM, <nanog-request@nanog.org> wrote:
Send NANOG mailing list submissions to nanog@nanog.org
This sort of thing happens 'often' ('XXX is not available, wtf?') should there be some set of troubleshooting steps followed, like a list of thing you'd do in order to show you'd troubleshot the problem and it wasn't "your problem"? Something along the lines of: o whois output o dig NS output o dig +trace output o 'downforeveryoneorjustme.com' says things are tango-uniform o other... reported such that others can either refute usefully or corroborate. -chris On Sat, Feb 18, 2012 at 4:46 PM, Israel G. Lugo <israel.lugo@lugosys.com> wrote:
Likewise, working here.
$ dig +trace www.facebook.com
; <<>> DiG 9.7.0-P1 <<>> +trace www.facebook.com ;; global options: +cmd . 240259 IN NS b.root-servers.net. . 240259 IN NS g.root-servers.net. . 240259 IN NS i.root-servers.net. . 240259 IN NS c.root-servers.net. . 240259 IN NS f.root-servers.net. . 240259 IN NS d.root-servers.net. . 240259 IN NS l.root-servers.net. . 240259 IN NS m.root-servers.net. . 240259 IN NS j.root-servers.net. . 240259 IN NS e.root-servers.net. . 240259 IN NS a.root-servers.net. . 240259 IN NS h.root-servers.net. . 240259 IN NS k.root-servers.net. ;; Received 272 bytes from 192.168.100.1#53(192.168.100.1) in 1 ms
com. 172800 IN NS a.gtld-servers.net. com. 172800 IN NS b.gtld-servers.net. com. 172800 IN NS c.gtld-servers.net. com. 172800 IN NS d.gtld-servers.net. com. 172800 IN NS e.gtld-servers.net. com. 172800 IN NS f.gtld-servers.net. com. 172800 IN NS g.gtld-servers.net. com. 172800 IN NS h.gtld-servers.net. com. 172800 IN NS i.gtld-servers.net. com. 172800 IN NS j.gtld-servers.net. com. 172800 IN NS k.gtld-servers.net. com. 172800 IN NS l.gtld-servers.net. com. 172800 IN NS m.gtld-servers.net. ;; Received 494 bytes from 2001:7fd::1#53(k.root-servers.net) in 65 ms
facebook.com. 172800 IN NS ns1.facebook.com. facebook.com. 172800 IN NS ns2.facebook.com. facebook.com. 172800 IN NS ns3.facebook.com. facebook.com. 172800 IN NS ns4.facebook.com. facebook.com. 172800 IN NS ns5.facebook.com. ;; Received 204 bytes from 192.48.79.30#53(j.gtld-servers.net) in 361 ms
www.facebook.com. 86400 IN NS glb2.facebook.com. www.facebook.com. 86400 IN NS glb1.facebook.com. ;; Received 104 bytes from 66.220.145.65#53(ns5.facebook.com) in 206 ms
www.facebook.com. 120 IN A 69.63.190.22 ;; Received 50 bytes from 69.171.255.10#53(glb2.facebook.com) in 146 ms
On 02/18/2012 09:39 PM, John Peach wrote:
On Sat, 18 Feb 2012 13:32:42 -0800 Everett Batey <efbatey@gmail.com> wrote:
facebook.com DNS not found 20120218 2125 UTC Is there any outage information for DNS for facebook.com / www.facebook.com ? "Oops! Google Chrome could not find www.facebook.com" Not here
dig +trace www.facebook.com
; <<>> DiG 9.7.3 <<>> +trace www.facebook.com ;; global options: +cmd . 157853 IN NS d.root-servers.net. . 157853 IN NS j.root-servers.net. . 157853 IN NS c.root-servers.net. . 157853 IN NS f.root-servers.net. . 157853 IN NS b.root-servers.net. . 157853 IN NS l.root-servers.net. . 157853 IN NS h.root-servers.net. . 157853 IN NS m.root-servers.net. . 157853 IN NS a.root-servers.net. . 157853 IN NS k.root-servers.net. . 157853 IN NS g.root-servers.net. . 157853 IN NS e.root-servers.net. . 157853 IN NS i.root-servers.net. ;; Received 228 bytes from 192.168.1.2#53(192.168.1.2) in 3 ms
com. 172800 IN NS b.gtld-servers.net. com. 172800 IN NS a.gtld-servers.net. com. 172800 IN NS f.gtld-servers.net. com. 172800 IN NS c.gtld-servers.net. com. 172800 IN NS j.gtld-servers.net. com. 172800 IN NS h.gtld-servers.net. com. 172800 IN NS l.gtld-servers.net. com. 172800 IN NS k.gtld-servers.net. com. 172800 IN NS g.gtld-servers.net. com. 172800 IN NS m.gtld-servers.net. com. 172800 IN NS i.gtld-servers.net. com. 172800 IN NS e.gtld-servers.net. com. 172800 IN NS d.gtld-servers.net. ;; Received 494 bytes from 192.5.5.241#53(f.root-servers.net) in 99 ms
facebook.com. 172800 IN NS ns1.facebook.com. facebook.com. 172800 IN NS ns2.facebook.com. facebook.com. 172800 IN NS ns3.facebook.com. facebook.com. 172800 IN NS ns4.facebook.com. facebook.com. 172800 IN NS ns5.facebook.com. ;; Received 204 bytes from 192.33.14.30#53(b.gtld-servers.net) in 208 ms
www.facebook.com. 86400 IN NS glb1.facebook.com. www.facebook.com. 86400 IN NS glb2.facebook.com. ;; Received 104 bytes from 66.220.151.20#53(ns3.facebook.com) in 91 ms
www.facebook.com. 120 IN A 69.171.234.96 ;; Received 50 bytes from 69.171.255.10#53(glb2.facebook.com) in 20 ms
On Fri, Feb 17, 2012 at 11:26 PM, <nanog-request@nanog.org> wrote:
Send NANOG mailing list submissions to nanog@nanog.org
----- Original Message -----
From: "Christopher Morrow" <morrowc.lists@gmail.com>
This sort of thing happens 'often' ('XXX is not available, wtf?')
should there be some set of troubleshooting steps followed, like a list of thing you'd do in order to show you'd troubleshot the problem and it wasn't "your problem"? Something along the lines of:
o whois output o dig NS output o dig +trace output o 'downforeveryoneorjustme.com' says things are tango-uniform o other...
reported such that others can either refute usefully or corroborate.
That's our ruleset on Outages; I repost it every so often (optimally monthly, though it's not automated yet...) Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274
On 2/18/2012 4:32 PM, Everett Batey wrote:
facebook.com DNS not found 20120218 2125 UTC Is there any outage information for DNS for facebook.com / www.facebook.com ? "Oops! Google Chrome could not find www.facebook.com"
I have had two reports of "can't get to facebook" from campus today, not exactly from 3rd-tier helpdesk techs mind you, but a reasonably reputable source. "Traceroute stops at 127.0.0.1" (yeah, I know). Works fine from campus for me, and they say the machine does "nslookup" a Facebook CDN provider IP (69.171.234.96). They can go anywhere else, no problem. Verified they have our DHCP server and internal recursive DNS servers so it's not an issue at that level. I'm "ONLY" bringing this up as my spidey-sense is wondering if there is some facebook-captive malware or browser plugin floating about? Ring any bells? If nothing else comes in I'm going to write it off as a Sunday evening hallucination and check it again tomorrow :) Jeff
Please feel free to unicast me if you ever see any reproducible issues. -Callahan On Sun, Feb 19, 2012 at 5:01 PM, Jeff Kell <jeff-kell@utc.edu> wrote:
On 2/18/2012 4:32 PM, Everett Batey wrote:
facebook.com DNS not found 20120218 2125 UTC Is there any outage information for DNS for facebook.com / www.facebook.com ? "Oops! Google Chrome could not find www.facebook.com"
I have had two reports of "can't get to facebook" from campus today, not exactly from 3rd-tier helpdesk techs mind you, but a reasonably reputable source. "Traceroute stops at 127.0.0.1" (yeah, I know).
Works fine from campus for me, and they say the machine does "nslookup" a Facebook CDN provider IP (69.171.234.96). They can go anywhere else, no problem. Verified they have our DHCP server and internal recursive DNS servers so it's not an issue at that level.
I'm "ONLY" bringing this up as my spidey-sense is wondering if there is some facebook-captive malware or browser plugin floating about?
Ring any bells?
If nothing else comes in I'm going to write it off as a Sunday evening hallucination and check it again tomorrow :)
Jeff
participants (7)
-
Callahan Warlick -
Christopher Morrow -
Everett Batey -
Israel G. Lugo -
Jay Ashworth -
Jeff Kell -
John Peach