781–790 of 1001 posts
Earlier quoted context omitted.
If only the news reporting was not as stupid as "internet is not working at UPC", instead of DNS resolvers at UPC crashed, here's what you can do... Anyway, I didn't even notice since I run knot-resolver at home. I wonder what it will be like connecting Facebook back to the internet, thundering herd and everything...
I suspect that the DNS aspect will be fine. The middle DNS servers only need one valid response to cache it for $TTL, but they can't cache SERVFAIL.
Will not that be an issue? Re-enabling routing to such a massive internet service...
- https://en.wikipedia.org/wiki/Facebook_onion_address
- facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion
Earlier quoted context omitted.
> the people with physical access is separate from the people with knowledge of [...] Welcome to the brave new world of troubleshooting. This will seriously bite us one day.
folks with physical access are also denied. source - https://twitter.com/YourAnonOne/status/1445100431181598723
If it is an DNS error, why is the .onion site also offline? - https://en.wikipedia.org/wiki/Facebook_onion_address - facebookwkhpilnemxj7asaniu7vnjjbiltxjqhye3mhbshg7kx5tfyd.onion
Earlier quoted context omitted.
I can't fathom how they didn't plan for this. In any business of size, you have to change configuration remotely on a regular basis, and can easily lock yourself out on a regular basis. Every single system has a local user with a random password that we can hand out for just this kind of circumstance...
> I can't fathom how they didn't plan for this Maybe because they were planning for a million other possible things to go wrong, likely with higher probability than this. And busy with each day's pressing matters.