-
chiakin103
- 1914
- 10
- 1
- 0
-
- いいね！0
NHKニュース
@nhk_news
フェイスブックやインスタグラムなどで障害 影響は世界的か #nhk_news www3.nhk.or.jp/news/html/2021…
2021-10-05 04:01:01ドメイン？
Baddies 🥵🍑
@HottiePromo
So, someone deleted large sections of the routing....that doesn't mean Facebook is just down, from the looks of it....that means Facebook is GONE. pic.twitter.com/OCZWPD2okw
2021-10-05 04:11:49
拡大
hinsuke(void)
@hinsuke
「続報 ― DNS (インターネットのドメイン名登録システム) の記録から、facebook.com や instagram.com が世界規模の配信テーブルから削除されていることがわかる。」
2021-10-05 03:06:05ドメインが売りに出されている？
吉川剛史/たけさん
@TakefumiY
ドメインがDNSから削除されて売りに出されているとか。なんか通常の障害とは違う。株価の落ち方もおかしい。アメリカでは主要携帯サービスにも障害発生。 Twitterは生きている。 #facebookdown #Facebook不具合 twitter.com/nhk_news/statu…
2021-10-05 05:56:25
JOÃO
@Joo00556315
BIZARRO: DOMÍNIO do Facebook à venda ?! O registro Whois do Domaintools aparentemente exibe um banner que mostra que o domínio do site pode ser adquirido! pic.twitter.com/6UyGUPyJTl
2021-10-05 07:37:15
拡大
売りに出されているは、誤解のよう。
neuro
@evilneuro
@alexhern don't forget that facebook are their own domain name registrar (registrarsafe.com), so whois lookups on their domains would fail, leading to some whois sites thinking they were available and purchaseable.
2021-10-05 06:40:47whois ?
ちあきん１０３🚁
@chiakin103
変だなぁ。 Facebook.com のwhois 出るところと、 出ない所がある けど、 networksolutions に出てこないってのは？ トヨタも出てこない netsol の仕様なんかな？ 情報出さない？ 自分のドメインは、出た。。 pic.twitter.com/1PrDcgk3Va
2021-10-05 07:11:08
拡大
拡大
拡大
拡大
Backorderとは、空いたら売るよって意味で、今売りに出してるでは無い。
networksolutions ではそう。
でも、ドメインまわり、DNSまわりは変な気がする。
追記します
確かに、こちらのページが判りやすいです。
Understanding How Facebook Disappeared from the Internet
Matthew Prince 🌥
@eastdakota
Here's our best explanation from what we can see on how @Facebook disappeared from the Internet: blog.cloudflare.com/october-2021-f…
2021-10-05 06:11:58
0xRahul
@omw_to_the_moon
@eastdakota @Facebook Two questions: 1. Did this impact (non fb) DNS as a whole? Since without facebook’s DNS servers, I assume routing across networks became difficult? 2. Wanted to clarify what the phrase “Facebook DNS servers” mean Just graduated in Comp Sci so still getting a hang of this stuff!
2021-10-05 08:50:02
Matthew Prince 🌥
@eastdakota
@iamRahul20x @Facebook There are authoritative and recursive DNS servers. Simplistically, businesses putting content online need authoritative servers; individuals surfing content online need recursive DNS servers. 1/N
2021-10-05 08:57:21
Matthew Prince 🌥
@eastdakota
@iamRahul20x @Facebook All domains must have an authoritative DNS server. It is the authority to say where content for a particular domain (e.g., Facebook.com or Google.com or Bobsblog.info or whatever) lives. 2/N
2021-10-05 08:58:47
Matthew Prince 🌥
@eastdakota
@iamRahul20x @Facebook In most cases, domain owners use a third party service to run their authoritative DNS server. Examples include Cloudflare, DynDNS, UltraDNS, GoDaddy, etc. But it’s possible to run your own authoritative DNS servers. That’s what Facebook does. 3/N
2021-10-05 09:00:38
Matthew Prince 🌥
@eastdakota
@iamRahul20x @Facebook Facebook’s Authoritative DNS only responds to queries for Facebook’s own domains. So, to answer your first question, no, when it went offline, it generally didn’t disrupt anything other than Facebook. 4/N
2021-10-05 09:02:31
Matthew Prince 🌥
@eastdakota
@iamRahul20x @Facebook But Facebook is so big that it’s not that simple. To understand, you need to understand a bit about DNS queries work. The way a DNS query goes when you’re trying to access Facebook.com is your device->your recursive DNS provider->Facebook’s authoritative provider. 5/N
2021-10-05 09:05:06
Matthew Prince 🌥
@eastdakota
@iamRahul20x @Facebook For most people, their recursive provider is provided automatically by their ISP. Some use a service like Cloudflare’s 1.1.1.1 or Google’s 8.8.8.8. You can also run your own recursive DNS provider. Regardless, it’s job is to query the authoritative provider and cache results. 6/N
2021-10-05 09:08:00
Matthew Prince 🌥
@eastdakota
@iamRahul20x @Facebook Problem is, when a recursive DNS provider gets an error back it often will tell the devices using it to check back again soon. This meant that hundreds of millions of devices were getting bad results for Facebook’s domains and then checking them again and again. 7/N
2021-10-05 09:10:03
Matthew Prince 🌥
@eastdakota
@iamRahul20x @Facebook To give you a sense of scale, 1.1.1.1 saw a 30x increase in DNS queries over normal. We have the capacity to handle the extra load, but some recursive providers threw errors or got very slow. 8/N
2021-10-05 09:11:40
Matthew Prince 🌥
@eastdakota
@iamRahul20x @Facebook So that’s why for some even services that weren’t Facebook’s may have appeared to be slow or broken. As for your second question, it’s Facebook’s Authoritative DNS servers. Hope that clarifies. 9/9
2021-10-05 09:13:31