[outages] Godaddy / Premium DNS outage?

[francis.daigneault at bell.ca]

Your right! perhaps DDOS does not mean any data have been compromise, it simply mean someone decide to piss you off.., and personally I prefer honesty, or more detail answer then "corrupted data" which is too easy.. let see what they going to say on that one.. 

http://pastebin.com/WMb4Qg7H

I guess it's a internal leak.. I'm not good enough in programation to say if this is fake or real or publicly available, clearly there missing stuff.. like the DB :) perhaps for me it appear a bit more serious and making sense then the godaddy story about yesterday failure. 


-=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--
Francis Daigneault (CCNP,MCSE,ECSA|LPT)
KNOWLEDGE IS FREE !

 


-----Original Message-----
From: Cary Smith [mailto:csmith at pickmta.com] 
Sent: September-11-12 4:40 PM
To: Corey Quinn; Daigneault, Francis (P008790)
Cc: outages at outages.org
Subject: RE: [outages] Godaddy / Premium DNS outage?

I'm not surprised Go-Daddy went in the direction of "internal network events that corrupted router data tables". It is definitely the lesser of the two evils. To come out and admit they were hacked or experienced a DDOS would make Customers feel their information on Go-Daddy servers was potentially compromised. Hence the CEO's statement, " At no time was any customer data at risk or were any of our systems compromised."

Unless there's a government investigation, which is doubtful, none of us will really ever know what truly happened.

Cary W. Smith
MTA
1567 East 93rd. Avenue
Merrillville, IN 46410
Office - 219-750-1803
Cell - 219-765-1251
e-mail - cary at pickmta.com


-----Original Message-----
From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On Behalf Of Corey Quinn
Sent: Tuesday, September 11, 2012 1:02 PM
To: francis.daigneault at bell.ca
Cc: outages at outages.org
Subject: Re: [outages] Godaddy / Premium DNS outage?

Frankly, "we were ddos'd" is a much better sell than "we screwed up our internal systems horribly because we're idiots.". Surprised they went this direction.

On Sep 11, 2012, at 10:53 AM, "francis.daigneault at bell.ca" <francis.daigneault at bell.ca> wrote:

> It's the easy answer to avoid admitting they where DDOS, when you can't explain something or you don't want to admit something blame it on "corruption"
>
> The outages start and stop at the time predicted by the hacker who "admit" it.. how could that happen.. coincidence ?
>
>
> -=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--
> Francis Daigneault (CCNP,MCSE,ECSA|LPT) KNOWLEDGE IS FREE !
>
>
>
>
> -----Original Message-----
> From: outages-bounces at outages.org [mailto:outages-bounces at outages.org]
> On Behalf Of Seth Mattinen
> Sent: September-11-12 1:48 PM
> To: outages at outages.org
> Subject: Re: [outages] Godaddy / Premium DNS outage?
>
> On 9/11/12 10:39 AM, Ben Carleton wrote:
>> "corrupted router data tables..." Any ideas on what this refers to? BGP?
>>
>
> It's either referring to a BGP/OSPF/IS-IS (insert dynamic routing
> protocol here) bug or a line of corporate-speak BS that sounds
> technical enough to where most people aren't going to ask for details.
>
> ~Seth
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages

_______________________________________________
Outages mailing list
Outages at outages.org
https://puck.nether.net/mailman/listinfo/outages
________________________________

DISCLAIMER: The information in this message is considered confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error.