[150233] in North American Network Operators' Group
Re: facebook.com DNS not found 20120218 2125 UTC
daemon@ATHENA.MIT.EDU (Callahan Warlick)
Sun Feb 19 20:21:02 2012
In-Reply-To: <4F419B7D.5040004@utc.edu>
Date: Sun, 19 Feb 2012 17:20:05 -0800
From: Callahan Warlick <callahanwarlick@gmail.com>
To: Jeff Kell <jeff-kell@utc.edu>
Cc: nanog@nanog.org, Everett Batey <efbatey@gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
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 =A0facebook.com / www.facebo=
ok.com
>> =A0?
>> =A0 "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. =A0"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). =A0They can go anywhere else,
> no problem. =A0Verified 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
>
