Facebook-owned sites were down

Post by robalfonso » Mon, Oct 04, 2021, 9:45 PM UTC

john37386 wrote: post #851

robalfonso wrote: post #827

Earlier quoted context omitted.

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…

Post by wolverine876 » Mon, Oct 04, 2021, 9:46 PM UTC

metadaemon wrote: post #837

okwubodu wrote: post #682

Earlier quoted context omitted.

I don’t know how true it is but a few reports claim employees can’t get into the building with their badges.

I've heard on Blind this is unrelated, more of a Covid restriction issue.

Post by amediauk1 » Mon, Oct 04, 2021, 9:47 PM UTC

  1     1 ms     1 ms     1 ms  eehub.home [192.168.1.254]
  2     3 ms     3 ms     3 ms  172.16.14.63
  3     \*        5 ms     3 ms  213.121.98.145
  4     5 ms     3 ms     4 ms  213.121.98.144
  5    17 ms     8 ms    18 ms  87.237.20.142
  6     8 ms     6 ms     7 ms  lag-107.ear3.London2.Level3.net [212.187.166.149]
  7     \*        \*        \*     Request timed out.
  8     \*        \*        \*     Request timed out.
  9     7 ms     7 ms     6 ms  be2871.ccr42.lon13.atlas.cogentco.com [154.54.58.185]
 10    70 ms    69 ms    70 ms  be2101.ccr32.bos01.atlas.cogentco.com [154.54.82.38]
 11    73 ms    73 ms    74 ms  be3600.ccr22.alb02.atlas.cogentco.com [154.54.0.221]
 12    84 ms    85 ms    84 ms  be2879.ccr22.cle04.atlas.cogentco.com [154.54.29.173]
 13    90 ms    90 ms    90 ms  be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129]
 14   143 ms   142 ms   143 ms  po111.asw02.sjc1.tfbnw.net [173.252.64.102]
 15   114 ms   119 ms   114 ms  be3036.ccr22.den01.atlas.cogentco.com [154.54.31.89]
 16   125 ms   126 ms   124 ms  be3038.ccr32.slc01.atlas.cogentco.com [154.54.42.97]
 17    91 ms    92 ms    91 ms  po734.psw03.ord2.tfbnw.net [129.134.35.143]
 18    91 ms    93 ms    90 ms  157.240.36.97
 19    74 ms    74 ms    73 ms  a.ns.facebook.com [129.134.30.12]

Post by wolverine876 » Mon, Oct 04, 2021, 9:49 PM UTC

FearNotDaniel wrote: post #828

still_grokking wrote: post #669

Earlier quoted context omitted.

You mean the same problem as when GMail goes down and Googlers can't reach each other? I guess good decentralized public communication services could solve those issues for everybody.

Anyone remember the 90s? There was this thing called the Information Superhighway, a kind of decentralised network of networks that was designed to allow robust communications without a single point of failure. I wonder what happened to that...?

Post by alexvoda » Mon, Oct 04, 2021, 9:50 PM UTC

chungy wrote: post #464

Even Facebook's Onion site isn't working: http://facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5t... Fascinating simply that it's apparently not just a DNS issue.