An anonymous reader writes:
My name is Jonathan Swift, but I don't remember my password.
Two completely unrelated groups of name servers, seven servers in total, suddenly stopped reponding to pings at the same time.
The 8-1-1 "Call Before You Dig" number is provided for the specific purpose of preventing this from happening, and not only does not offer a way to report that it atuallly just happened but is also closed tor the day.
The 9-1-1 Emergency Reponse operator got all pissed off when I tried to tell him that half of North America would find inself unable to speak to the other half should a national emergency happen right around now. They guy thought I was delusional when I struggled desperately to get him to find me a backbone Network Operations Center, then hung up on me.
But I knew my friends as Slashdot would be happy to give me some love. Please report your physical location, ping each of the following nameservers, the report whether or not each specific one responds:
I'm near the intersection of Blossom and Snell in South San Jose California..
I cannot ping any of these. I had just brought up a site for which the second group is servers. When I reloaded the page, all five of its servers failed to respond.
First
- 209.151.88.206 — ns.ez-web-hosting.com
- 209.151.88.216 — ns1.ez-web-hosting.com
Second
- NS0.DNSMADEEASY.COM
- NS1.DNSMADEEASY.COM
- NS2.DNSMADEEASY.COM
- NS3.DNSMADEEASY.COM
- NS4.DNSMADEEASY.COM
When I can hunt down that gifted emergency response professional, I'm going to give him a clue as to what emergency response really is. Don't Get Me Started. Just Don't.