Re: Akamai DNS Issue?

[Matt Levine <matt-keyword-nanog.aedae7 () deliver3 com>]

So, were google/yahoo able to get verisign to push a change to the gtld 
registry to update their NS's, or was it just done during a scheduled 
update?

How much clout does one need to have the com zone 
updated/pushed/reloaded? ;)


On Jun 16, 2004, at 10:28 PM, Hannigan, Martin wrote:

> 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,
>
> --
> Martin Hannigan                         (c) 617-388-2663
> VeriSign, Inc.                          (w) 703-948-7018
>                                          <http://www.verisign.com/>
>
>
>
> -----Original Message-----
> From: owner-nanog () merit edu <owner-nanog () merit edu>
> To: Patrick W.Gilmore <patrick () ianai net>; nanog () merit edu 
> <nanog () merit edu>
> CC: Patrick W.Gilmore <patrick () ianai net>
> Sent: Wed Jun 16 16:51:34 2004
> Subject: Re: Akamai DNS Issue?
>
>
>
> ----- Original Message -----
> From: "Patrick W.Gilmore" <patrick () ianai net>
> To: <nanog () merit edu>
> Cc: "Patrick W.Gilmore" <patrick () ianai net>
> 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 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 equally important. We even went as far as asking Paul
> > > Vixie if
> > > we were routed to the blackhole. It is the same issue, just a 
> > > different
> > > flavor.
> >
> > I really hate getting into flame wars, but I am interested in data
> > about this last event.
> >
> > You say "it is the same issue, just a different flavor".  I am
> > wondering if you meant the problem Tuesday morning is the same problem
> > you had weeks ago, or if the problem you had weeks ago is the same as
> > the problem you are having with Overture / Yahoo / SBC?  It is unclear
> > to me exactly what you meant, and "Details are Important". :)
> >
> > If you honestly believe you had the same problem weeks ago that
> > everyone else experienced Tuesday morning, please give us some more
> > information.  I do not believe Akamai has ever had the type of problem
> > experienced yesterday.
> >
> > --
> > TTFN,
> > patrick
>
> 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
> router-level or DNS-level ) as we were experiencing lack of resolution 
> to
> yahoo, and google. We noted that google adwords were using a different 
> dns
> than akamai and could be seen. The problem continued intermittently
> throughout the week, yet nobody put the questions we were asking along 
> with
> the issues taking place from Akamai within dispite our pleas, and 
> requests
> to resolve this issue. We performed traceroutes, pings, bgp summarys 
> making
> sure we weren't being blocked before we started pointing any fingers 
> and
> asking any stupid questions yet we still were ignored and could of 
> helped
> Akamai prevent such occurances from happening. It is us who is paying 
> google
> $186,000 a quarter and Yahoo $146,000 a quarter in advertising, you'd 
> think
> that someone would look our way and see we're having troubles rather 
> than
> walking on while we were being mugged. Rather than being treated as 
> mere
> babble we could of provided our logs as we were working within over 30
> looking glasses trying to see what was happening and where the problem 
> were
> occuring.
>
> - Pete