Replies

I've been messing with DNS professionally going on 30 years now... actually longer. But anyway, I looked up the NS RRs for facebook.com DNS and queried them DIRECTLY for facebook.com SOAs from four different networks that I have access to, and I'm unable to get a response from any of the four networks.

So I'm not entirely certain what happened to them, but at least at this point, it's safe to say that their DNS is FUBAR. Too bad... couldn't have happened to a nicer bunch of people. :-)

I would have thought a company like Facebook would have had monitors in place to detect this sort of tweaking and pre-existing relationships with the big DNS hosts to get it fixed quickly if it happened.

But now that this has gone on for several hours, I’m starting to wonder how it is that it hasn’t been fixed yet unless it was intentional by Facebook (for some reason I don’t comprehend). If it was some sort of hack, it really should have been fixed by now at least on the top level servers. Just thinking about the ad revenue they’re losing is pretty mind-blowing - it would certainly justify any resources necessary to get this fixed.