Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Facebook-owned sites were down

facebook.com

Post reply on HN
Print view View original

851–860 of 1001 posts

Re: Facebook-owned sites were down

#851

Post by john37386 »

robalfonso wrote: post #827
Animats wrote: post #805

Earlier quoted context omitted.

"facebook.com" is registered with "registrarsafe.com" as registrar. "registrarsafe.com" is unreachable because it's using Facebook's DNS servers and is probably a unit of Facebook. "registrarsafe.com" itself is registered with "registrarsafe.com". I'm not sure of all the implications of those circular dependencies, but it probably makes it harder to get things back up if the whole chain goes down. That's also probabl…

This is not completely accurate. The whole reason a registrar with domain abc.com can use ns1.abc.com is because glue records are established at the registry, this allows a bootstrap that keeps you in from a circular dependency. All that said it’s usually a bad idea, for someone as large as Facebook they should have nameservers across zones ie a.ns.fb.com b.ns.fb.org c.ns.fb.co Etc…

There is always a step which involve to email the domain when a domain update its information with the registrar. In this case, facebook.com and registrarsafe.com are managed by the same NS. You need these NS to query the MX to send that update approval by email and unblock the registrar update. Glue records are more for performance than to make that loop. I'm maybe missing something but, hopefully they won't need to send an email to fix this issue.

Re: Facebook-owned sites were down

#853

Post by saltyfamiliar »

MrYellowP wrote: post #642

I keep trying to submit to HN but I keep getting an error. What's wrong with the internet? FaceBook is down. My friend from Slovenia is having trouble with discord. It eats his messages. I can't load photos from my friend in telegram and the messages take a relatively long time - multiple seconds! - to get received. TrackMania players have talked about having input lag. ycombinator is really slow and reports an error…

I'm having issues with telegram as well. Images won't send and the app continuously says "updating" on the top status bar.

How could facebook dns issues cause this?

Re: Facebook-owned sites were down

#854

Post by tacker2000 »

dividedbyzero wrote: post #849
rootusrootus wrote: post #764

Earlier quoted context omitted.

I just got off a short pre-interview conversation with a manager at Instagram and he had to dial in with POTS. I got the impression that things are very broken internally.

What is POTS?

Plain Old Telephone System

Re: Facebook-owned sites were down

#855

Post by progbits »

sjg007 wrote: post #600
tiborsaas wrote: post #376

Earlier quoted context omitted.

"I believe the original change was 'automatic' (as in configuration done via a web interface). However, now that connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally." Hmm, could be a UI/UX bug then :)

Seems odd to not have a redundant backdoor on a different network interface. Maybe that is too big of a security risk but idk.

You know how after changing resolution and other video settings you get a popup "do you want to keep these changes?" with a countdown and automatic revert in case you managed to screw up and can't see the output anymore?

Well, I wonder why a router that gets a config update but then doesn't see any external traffic for 4 hours doesn't just revert back to the last known good config...

Re: Facebook-owned sites were down

#856

Post by boshomi »

mdtancsa wrote: post #749
Animats wrote: post #628

There's still no connectivity to Facebook's DNS servers: > traceroute a.ns.facebook.com traceroute to a.ns.facebook.com (129.134.30.12), 30 hops max, 60 byte packets 1 dsldevice.attlocal.net (192.168.1.254) 0.484 ms 0.474 ms 0.422 ms 2 107-131-124-1.lightspeed.sntcca.sbcglobal.net (107.131.124.1) 1.592 ms 1.657 ms 1.607 ms 3 71.148.149.196 (71.148.149.196) 1.676 ms 1.697 ms 1.705 ms 4 12.242.105.110 (12.242.105.110)…

Its partially there. C and D are still not in the global tables according to routeviews ie. 185.89.219.12 is still not being advertised to anyone. My peers to them in Toronto have routes from them, but not sure how far they are supposed to go inside their network. (past hop 2 is them) % traceroute -q1 -I a.ns.facebook.com traceroute to a.ns.facebook.com (129.134.30.12), 64 hops max, 48 byte packets 1 torix-core1-10G…

Kevin Beaumont:

   »The Facebook outage has another major impact: lots of mobile apps constantly poll Facebook in the background = everybody is being slammed who runs large scale DNS, so knock on impacts elsewhere the long this goes on.«
https://twitter.com/GossiTheDog/status/1445118907187175427

Re: Facebook-owned sites were down

#858

Post by woofcat »

dividedbyzero wrote: post #849
rootusrootus wrote: post #764

Earlier quoted context omitted.

I just got off a short pre-interview conversation with a manager at Instagram and he had to dial in with POTS. I got the impression that things are very broken internally.

What is POTS?

Plain old telephone system. Aka a phone.

Re: Facebook-owned sites were down

#859

Post by terramex »

dividedbyzero wrote: post #849
rootusrootus wrote: post #764

Earlier quoted context omitted.

I just got off a short pre-interview conversation with a manager at Instagram and he had to dial in with POTS. I got the impression that things are very broken internally.

What is POTS?

Plain old telephone service https://en.wikipedia.org/wiki/Plain_old_telephone_service
Post reply on HN