The GoDaddy DNS outage which began earlier today will likely be hijacked by Chicken Little as further proof the cloud computing sky is falling. A DNS outage could cause a lot of interference to a company, especially one has busy as Go Daddy, it is for this reason among others that many companies that work with a network look at DNS monitoring to help keep track of their servers. If you are interested in finding out more about dns monitoring you may want to visit somewhere similar to https://www.thousandeyes.com/solutions/dns-monitoring to learn more.
For those of you not yet aware of the issue, which is probably a good thing, the GoDaddy DNS outage is the result of denial of service attack launched by @AnonymousOwn3r.
GoDaddy Update (9/12/12)
GoDaddy.com CEO denies the service interruptions were the result of being hacked. In a statement released yesterday by Scott Wagner, GoDaddy CEO, the outage was attributed to technical problems that resulted in corrupted router tables. Wagner also reassured customers that at no time was any sensitive customer data compromised. These sorts of attacks can happen anytime, anywhere. They can even be done on home routers, which is why having a secure password and robust security installed is very important. If you’d like more information, click here. Back to GoDaddy, though.
@AnonymousOwn3r turned to Twitter to announce he had initiated a takedown of GoDaddy.com earlier today.
Can I admit that I think there is a certain flare to using Twitter in this way?
@AnonymousOwn3r made it clear he was acting alone and that the GoDaddy.com takedown was not the work of the Anonymous group. He even went so far as to Tweet corrections to writers throughout the day who got it wrong.
And so it began with GoDaddy.com issuing an alert over Twitter to its millions of customers affected by the DNS outage.
The lack of detail in the GoDaddy updates did not go unnoticed by the tech media who are ready to pronounce the end of the big domain registrar if they don’t handled this incident properly with customers.
GoDaddy DNS Outage
The GoDaddy DNS Outage affected more than the websites hosted by GoDaddy.com. The DNS takedown affected millions of domains registered through GoDaddy but hosted elsewhere that are still using GoDaddy for DNS. That is a very long list and includes lots of on-premise and cloud based email.
I imagine several colleges and universities found themselves among this group today where they purchased additional domains through GoDaddy.com for foundations, clubs and organizations or other special purposes.
So here we are at T+6 hours and the most recent GoDaddy updates indicates they are getting close to completing their recovery.
But a quick scan of the GoDaddy.com support forums reveals plenty of customers are nowhere near close to recovering which likely means several more hours or days of cleanup ahead.
OK, unlike the most recent Amazon EC2 outage, I am struggling just a bit to find a decent set of takeaways from today’s events.
In case I don’t come up with anything really meaningful I will at least use this as an opportunity for a gratuitous mention of Danika Patrick dropping to 11th in the Nationwide Series driver standings looking all anonymous in her GoDaddy.com gear.
Perhaps one takeaway is that for all the fears of cloud services the core Internet services still leave us most vulnerable.
Perhaps we might remind ourselves that hacktivism is a growing threat which places higher education at greater risk because of the high profile nature of university targets and generally more open systems.
Perhaps we might simply remind ourselves to do the basic housekeeping to keep track of all the domains we own and where we have our DNS pointed.
Where you unexpectedly impacted today and care to share a bit of what happened? Maybe you want to unload on how Danika Patrick doesn’t deserve to be in NASCAR. Just leave a comment.