On 15 Jun 2004, at 21:28, Stewart, William C (Bill), RTSLS wrote:
Daniel Golding suggested that the problem was that many folks are
sharing Akamai's magic DNS algorithms.
This doesn't appear to be a problem with magic algorithms - it appears
that they're sharing the _servers_,
and that the
Workarounds and defences already exist, and have been in use for a long
time.
long list removed
Failures in master servers can be mitigated by having several of them;
simultaneous failure of all master servers can be managed to some
degree using appropriate SOA timers, so that slave
peer, it would be difficult to
inject a malformed packet.
Cisco has made free software available to address this problem.
This advisory is available at
http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml.
Affected Products
=
Vulnerable Products
This issue affects all
On 16 Jun 2004, at 10:13, Mark Radabaugh wrote:
But you don't say how to avoid failures caused by massive confusion
when
maintaining a excessively complicated system
By isolating the complexity to small pockets, each of which is largely
invisible to the rest of the system, and reducing the
Mark Radabaugh wrote:
But you don't say how to avoid failures caused by massive confusion when
maintaining a excessively complicated system
I don't have much to offer for the excessively complicated case
(which I think the instant case is an example of), but there are
cases as complex and
On 6/15/04 9:28 PM, Stewart, William C (Bill), RTSLS [EMAIL PROTECTED]
wrote:
Daniel Golding suggested that the problem was that many folks are sharing
Akamai's magic DNS algorithms.
This doesn't appear to be a problem with magic algorithms - it appears that
they're sharing the _servers_,
http://www.overclockersclub.com/?read=8733819
The Akamai attacks started in the morning and it was detected by
Keynote Systems, a web tracking company that is able to track the load
and bandwidth on the Internet. According to Keynote they saw
an Internet performance issue this morning
...
They
David Kennedy CISSP wrote:
The Akamai attacks started in the morning and it was detected by
Keynote Systems, a web tracking company that is able to track the
load
and bandwidth on the Internet. According to Keynote they saw
an Internet performance issue this morning
...
Here's a link to a
He did provide a link
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 12:20 PM
To: [EMAIL PROTECTED]
Subject: RE: Akamai an Inside Job?
David Kennedy CISSP wrote:
The Akamai attacks started in the
At 08:23 AM 6/16/2004, David Kennedy CISSP wrote:
http://www.overclockersclub.com/?read=8733819
The Akamai attacks started in the morning and it was detected by
Keynote Systems, a web tracking company that is able to track the load
and bandwidth on the Internet. According to Keynote they saw
an
Hi all -
If you have no interest in Internet Peering in Asia, read no further.
Otherwise,...
Over the last year I have been working with the Peering Coordinator
Community, particularly those that have built into and throughout Asia, to
document what is *different* about peering in Asia as
I saw this coming two days ago but, nobody [Called]. Akamai's DNS was
failing apart and we thought that we were just being dns blackhole!
No, you didn't. You saw a different problem, asked me about it, and
didn't
send back any of the info I asked for.
Don't let truth and facts get in
--On Wednesday, June 16, 2004 1:26 PM -0400 Pete Schroebel
[EMAIL PROTECTED] wrote:
I saw this coming two days ago but, nobody [Called]. Akamai's DNS was
failing apart and we thought that we were just being dns blackhole!
No, you didn't. You saw a different problem, asked me about it, and
At 09:41 AM 6/16/2004 -0700, Brian Mulvaney wrote:
At 08:23 AM 6/16/2004, David Kennedy CISSP wrote:
http://www.overclockersclub.com/?read=8733819
[DMK: Source, beyond overclockers, unknown, reliability and accuracy
unknown.]
That's nonsense David. Keynote measurements can distinguish
On 6/16/04 11:23 AM, David Kennedy CISSP [EMAIL PROTECTED] wrote:
http://www.overclockersclub.com/?read=8733819
The Akamai attacks started in the morning and it was detected by
Keynote Systems, a web tracking company that is able to track the load
and bandwidth on the Internet. According
Is anyone aware of a non-akamized way to access google? Considering we've
had a few Akamai issues in the past couple months it could proove handy in
the future to be able to access google through non-Akamai channels. I
thought maybe the API access they provide may bypass it, but with a little
On Jun 16, 2004, at 1:26 PM, Pete Schroebel wrote:
With the Akamai issue we were seeing only partial resolution and since
we
pay Google a big wack of dough each month it is important for there
network
to resolve. Additionally, we have the same contracts with
Overture/Yahoo/SBC
so they are
I'd suggest working with Google if you feel you need some sort of out of
band access to them rather than asking here. I'm sure Google doesn't need
thousands of people picking weird random ways to access their clusters. :)
Is anyone aware of a non-akamized way to access google? Considering
On Wednesday, 2004-06-16 at 13:56 MST, Duncan Meakins
[EMAIL PROTECTED] wrote:
Is anyone aware of a non-akamized way to access google?
http://216.239.57.104
(No guarantee that that address will continue to work, but it currently
goes to one of their servers in Calif.)
Tony Rall
On Wed, Jun 16, 2004 at 04:28:37PM -0700, Tony Rall wrote:
On Wednesday, 2004-06-16 at 13:56 MST, Duncan Meakins
[EMAIL PROTECTED] wrote:
Is anyone aware of a non-akamized way to access google?
http://216.239.57.104
(No guarantee that that address will continue to work, but it
Jared Mauch wrote:
I think the question is truly this:
some of the dns responses that i saw had low ttls, should
they use a longer ttl?
the problems i saw were related to the data expiring from the cache,
some of this is to workaround broken clients/resolvers that will
- Original Message -
From: Patrick W.Gilmore [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Patrick W.Gilmore [EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 5:32 PM
Subject: Re: Akamai DNS Issue?
On Jun 16, 2004, at 1:26 PM, Pete Schroebel wrote:
With the Akamai issue we were
On Wednesday, 2004-06-16 at 20:02 AST, support services
[EMAIL PROTECTED] wrote:
On Wed, Jun 16, 2004 at 04:28:37PM -0700, Tony Rall wrote:
http://216.239.57.104
Yes, the old servers are still there but, they are out of date and not
in-sync with any other servers. They can act as
We have been experiencing this problem weeks ago, this is virtually under
the same spectrum of problems that Akamai via AKADNS.NET with their
corporate DNS servers that carry traffic for google, yahoo, msn, etc. When
we were asking if Akamai blacklisted/blackholed ip addresses ( we meant at
We have been experiencing this problem weeks ago, this is virtually
under
the same spectrum of problems that Akamai via AKADNS.NET with their
corporate DNS servers that carry traffic for google, yahoo, msn, etc.
When
we were asking if Akamai blacklisted/blackholed ip addresses ( we
meant at
Ok, but isn't this one of those things taken up better with google and
yahoo sales people?
Operationally, they have a large impact and they responded well.
If you only knew how many DDOS attacks your providers (all encompassed) see
and soak up, you'd be surprised.
YMMV
-M
Regards,
QA: Tom Leighton, chief scientist at Akamai
He talked about the nature of yesterday's apparent DDoS attack
News Story by Jaikumar Vijayan
JUNE 16, 2004 (COMPUTERWORLD) - Akamai Technologies Inc. said today that
the Domain Name System problems it encountered yesterday were the result of
a
27 matches
Mail list logo
