The recent Internet outage problem

Br. John wrote: The server for the site is not with GoDaddy but the domain is registered there and uses it's DNS.

Yes, I know, by "hosted" I meant DNS host. Sorry for the unclear wording there.

ren wrote: the problem wasn't DNS lookup.

The problem I was referring to was definitely a DNS problem. It's the first time I've ever seen the "nslookup" command time out. If it was merely an issue of the site being offline, then nslookup would have been able to resolve TOTJO's IP address from its DNS name (templeofthejediorder.org), even if I couldn't ping it or access it. But such was not the case.

ren wrote: (because I don't use DNS lookup on totjo and I experienced the issue) (also I took the site offline myself yesterday)

This issue did not occur yesterday (Wednesday). It occurred on Monday and affected thousands of GoDaddy DNS and email customers.

PloKoon wrote: As much as we want to overinflate this story.. it was actually an internl employee who took Go Daddy offline for a few...

My apologies if you perceived a desire to overinflate anything coming from me. I simply reported both sides of the incident with no bias toward either one. And unless you work for GoDaddy, then I'm not sure how you'd be in a position to know for sure that it was the result of some internal employee... Link(s) please?

I've been following the incident since it occurred, and there is no clear indication of what happened. Sure, GoDaddy says it was an internal problem, but really? Of course they would say that. They don't want to appear vulnerable. They have potential customers to consider.

In my experience you don't suddenly have catastrophic problems like that on accident. It typically requires malice and forethought. Still, could it have been purely an internal accident? Absolutely.

Fraternally in the Force,
-David

Accidents can happen...either way we have no way of knowing and just assuming it was a "hack" doesn't make it a hack, I myself managed to bring down every single computer in my school's network when I was a student...by accident.

But I guarantee you, the admins thought it was a "hack"

But it wasn't...Even the huge companies have accidents.

"that'd make no difference to where our server is hosted, especially seeing as we can't just unplug the router... "
I was giving the advice to users who got DoSed, but it seems that won't be a problem. colon capital D ()

Hmm well maybe there also was DNS issue, though I find this unlikely culprit. DNS gets cached, by ISPs, by browsers, etc, also, as I said, I eventually experienced the issue, but totjo is in my /etc/hosts. So definitely not (only)DNS. There was a problem with the routing, preventing me from tracerouting to Proteus' IP from the server for instance, and I also decided to do some cleanup and hard disk checks on the server. That's it.

@ FraterDavid

http://arstechnica.com/security/2012/09/godaddy-outage-caused-by-router-snafu-not-ddos-attack/

The company is here in Phoenix (i'm in Phx) so that's how I heard of it...

ren wrote: Hmm well maybe there also was DNS issue, though I find this unlikely culprit. DNS gets cached, by ISPs, by browsers, etc, also, as I said, I eventually experienced the issue, but totjo is in my /etc/hosts. So definitely not (only)DNS. There was a problem with the routing, preventing me from tracerouting to Proteus' IP from the server for instance, and I also decided to do some cleanup and hard disk checks on the server. That's it.

Fair enough. I didn't intend my initial post to imply only a DNS issue, but the report I read said it had affected DNS and email customers. -shrug-

PloKoon wrote: arstechnica.com/security/2012/09/godaddy...afu-not-ddos-attack/
The company is here in Phoenix (i'm in Phx) so that's how I heard of it...

Thank you for the link. I am glad to see further evidence that it was not a matter of hacking or DDoS.

Fraternally,
-David