Appologies to all, and the other DNSbls, I'm a little uptight about how long it is taking for the arrest of the DDoSer.
Yes he has been identified, and that's all I can say.
/ Mat
This morning, more often than not, nonexistent domain name access via
http is returning timeouts. Overload? DoS? It appears, for whatever
reason, that Verisign's scheme is not impervious to the inevitable
consequences of arrogant behavior.
Curt Akin wrote:
This morning, more often than not, nonexistent domain name access via
http is returning timeouts. Overload? DoS? It appears, for whatever
reason, that Verisign's scheme is not impervious to the inevitable
consequences of arrogant behavior.
The service seems to have experienced about 30 minute downtime about an hour ago.
On average, the redirect servers has responded in less than four seconds in the last
36 hours. This performance is far from what any commercial enterprise should provide.
Performance seems to be worst from 9 UTC to 22 UTC, with best hours to
access yourreallyreallynonexistentdomain.com are 1 to 6 UTC.
Pete
Repeated (though informal) testing over the last 90 minutes showed
that at one point, about one-third of attempted HTTP connections to
sitefinder took over one minute to complete or, in a few cases, failed
entirely.
Now only about one of every 5 or 10 connections is displaying that
behavior.
-Declan
I am not surprised at all. If VeriSign took their efforts and time to show us
some purported "recommendations" to abide to their new service, they better at
least deal with DoS pretty fast before more people get uptight.
-hc
I'm keeping track of sitefinder vs. google page load times, just for
giggles. You can see the results at:
http://mrtg.snark.net/http-time/
One thing thats missing is accounting for refused connections; I'll
have to put a little more thought into that.
matto