RE: Akamai DNS Issue?
Similar issues with Yahoo on and off since about 8:30am (EST). -Drew -----Original Message----- From: Leo Bicknell [mailto:bicknell@ufp.org] Sent: Tuesday, June 15, 2004 9:09 AM To: nanog@merit.edu Subject: Akamai DNS Issue?
From here neither www.google.com, nor www.apple.com work. Both seem to return CNAMES to akadns.net addresses (eg, www.google.akadns.net, www.apple.com.akadns.net), and from here all of the akadns.net servers listed in whois are failing to respond.
Can someone confirm from another location? Comments from Akamai? -- Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org
sbc/yahoo and them wee doing upgrades on their email last night could be moving things around to accomodate -Henry --- Drew Weaver <drew.weaver@thenap.com> wrote:
Similar issues with Yahoo on and off since about 8:30am (EST).
-Drew
-----Original Message----- From: Leo Bicknell [mailto:bicknell@ufp.org] Sent: Tuesday, June 15, 2004 9:09 AM To: nanog@merit.edu Subject: Akamai DNS Issue?
From here neither www.google.com, nor www.apple.com work. Both seem to return CNAMES to akadns.net addresses (eg, www.google.akadns.net, www.apple.com.akadns.net), and from here all of the akadns.net servers listed in whois are failing to respond.
Can someone confirm from another location? Comments from Akamai?
-- Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org
sbc/yahoo and them wee doing upgrades on their email last night could be moving things around to accomodate
-Henry
--- Drew Weaver <drew.weaver@thenap.com> wrote:
Similar issues with Yahoo on and off since about 8:30am (EST).
-Drew
-----Original Message----- From: Leo Bicknell [mailto:bicknell@ufp.org] Sent: Tuesday, June 15, 2004 9:09 AM To: nanog@merit.edu Subject: Akamai DNS Issue?
From here neither www.google.com, nor www.apple.com work. Both seem to return CNAMES to akadns.net addresses (eg, www.google.akadns.net, www.apple.com.akadns.net), and from here all of the akadns.net servers listed in whois are failing to respond.
Can someone confirm from another location? Comments from Akamai?
-- Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org
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! hmmmmm? -Peter
--On Tuesday, June 15, 2004 12:59 PM -0400 Pete Schroebel <crossfire@smsonline.net> 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 didn't send back any of the info I asked for. Don't let truth and facts get in the way of a good theory though!
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 the way of a good theory though!
Nope . . . Nobody "Called" (using the Telephone) [Details are Important] And . . I did reply to your e-mail, you may not have recieved it. Currently, I am working with AOL's ATDN with Compuserve Legacy (Ddos) and DNS Attacks as their "internal-only" servers are issuing attacks. 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. -Peter
--On Wednesday, June 16, 2004 1:26 PM -0400 Pete Schroebel <crossfire@smsonline.net> 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
didn't
send back any of the info I asked for.
Don't let truth and facts get in the way of a good theory though!
Nope . . . Nobody "Called" (using the Telephone) [Details are Important]
Oh, right. The phone number you didn't include in your email. OK then.
And . . I did reply to your e-mail, you may not have recieved it.
I'd check your maillogs then.
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
----- 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
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.
and, TECHNICALLY, what did you learn from all the measurements? randy
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, In addition to John responding to your Nanog request for help from Akamai, I also responded (privately) and did not hear anything from you. Did you ever open a ticket with the Akamai NOC or Customer Care, and if so, can you give me that ticket number? I doubt seriously that no one at Akamai listened. We've got two right here that responded and did not get a response, on a non standard channel. Standard channels are probably a much better place to go, and so I'd guess you had much better luck there. So, if you can send me the ticket number, we'll take this off Nanog and get it resolved. Thanks, Sean (Akamai NetArch Guy)
participants (7)
-
Drew Weaver -
Henry Linneweh -
John Payne -
Patrick W.Gilmore -
Pete Schroebel -
Randy Bush -
Sean Butler