On Thu, 2004-06-17 at 20:00, Paul Vixie wrote:
think stability.
I think recent events prove pretty well that Verisign GRS no longer gives
a crap about stability. Have we forgotten *.COM so quickly?
oh please. i was an publically critical of *.COM and *.NET, but that's a
policy
:00 PM
To: [EMAIL PROTECTED]
Subject: Re: Pushing GTLD zones [WAS: Akamai DNS Issue?]
think stability.
I think recent events prove pretty well that Verisign GRS no longer
gives a crap about stability. Have we forgotten *.COM so quickly?
oh please. i was an publically critical
PROTECTED]
CC: Patrick W.Gilmore [EMAIL PROTECTED]
Sent: Wed Jun 16 16:51:34 2004
Subject: Re: Akamai DNS Issue?
- 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
On Jun 17, 2004, at 11:22 AM, Matt Levine wrote:
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?
What makes you think an update at the GTLDs was required?
Try digging for google.com, then dig
Ya...didn't look at the setup before I posted, oh well..
I'll still pose the question as a theoretical one... say it was
ultradns rather than akadns (..or any substantially large website in
traffic having an authoritive DNS attack), would verisign be willing to
push changes for somebody 'big' ?
On Jun 17, 2004, at 11:37 AM, Matt Levine wrote:
Ya...didn't look at the setup before I posted, oh well..
I'll still pose the question as a theoretical one... say it was
ultradns rather than akadns (..or any substantially large website in
traffic having an authoritive DNS attack), would verisign
On Thu, Jun 17, 2004 at 11:49:20AM -0400, Patrick W Gilmore wrote:
On Jun 17, 2004, at 11:37 AM, Matt Levine wrote:
I'll still pose the question as a theoretical one... say it was
ultradns rather than akadns (..or any substantially large website in
traffic having an authoritive DNS
--On Thursday, June 17, 2004 16:07 + [EMAIL PROTECTED]
wrote:
think stability.
I think recent events prove pretty well that Verisign GRS no longer gives a
crap about stability. Have we forgotten *.COM so quickly?
think stability.
I think recent events prove pretty well that Verisign GRS no longer gives
a crap about stability. Have we forgotten *.COM so quickly?
oh please. i was an publically critical of *.COM and *.NET, but that's a
policy problem, not an operational problem. verisign has a
On 17 Jun 2004 18:00:02 +
Paul Vixie [EMAIL PROTECTED] wrote:
(note that verisign has amended their complaint against icann (since
the court dismissed the first one) and i'm now named as a
co-conspirator. if you reply to this message, there's a good chance
of your e-mail appearing in
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
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_,
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
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
- 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
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
]; [EMAIL PROTECTED] [EMAIL PROTECTED]
CC: Patrick W.Gilmore [EMAIL PROTECTED]
Sent: Wed Jun 16 16:51:34 2004
Subject: Re: Akamai DNS Issue?
- Original Message -
From: Patrick W.Gilmore [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Patrick W.Gilmore [EMAIL PROTECTED]
Sent: Wednesday, June 16
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?
Similar issues with Yahoo on and off since about 8:30am (EST).
-Drew
-Original Message-
From: Leo Bicknell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 15, 2004 9:09 AM
To: [EMAIL PROTECTED]
Subject: Akamai DNS Issue?
From here neither www.google.com, nor www.apple.com work. Both
I've noticed this for the past ~30 minutes.
(with news.yahoo).
hopefully it will be fixed soon.
- jared
On Tue, Jun 15, 2004 at 09:08:40AM -0400, Leo Bicknell wrote:
From here neither www.google.com, nor www.apple.com work. Both
seem to return CNAMES to
Confirmed from here. Google is back for us, yahoo, fedex, microsoft, and
others still out. As observed, all look to relate back to akadns.net.
-
Mark Rekai - INetU Managed Hosting - http://www.INetU.net
[EMAIL PROTECTED] - Phone:
On Tue, Jun 15, 2004 at 09:08:40AM -0400 Leo Bicknell([EMAIL PROTECTED]) wrote:
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
On Tue, Jun 15, 2004 at 09:08:40 -0400, Leo Bicknell wrote:
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
:[EMAIL PROTECTED] On
Behalf Of Leo Bicknell
Sent: Tuesday, June 15, 2004 9:09 AM
To: [EMAIL PROTECTED]
Subject: Akamai DNS Issue?
x
--
Leo Bicknell - [EMAIL PROTECTED] - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - [EMAIL PROTECTED], www.tmbg.org
Leo Bicknell wrote:
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
We are unable to make new resolutions from their servers
granite# host -t ns akadns.net
akadns.net name server zh.akadns.net
akadns.net name server eur3.akam.net
akadns.net name server zf.akadns.net
akadns.net name server zc.akadns.net
akadns.net name server asia3.akam.net
akadns.net name server
: Akamai DNS Issue?
On Tue, Jun 15, 2004 at 09:08:40AM -0400 Leo Bicknell([EMAIL PROTECTED])
wrote:
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
:
Name:www.google.akadns.net
Addresses: 216.239.51.147, 216.239.51.99, 216.239.51.104
Aliases: www.google.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Leo Bicknell
Sent: Tuesday, June 15, 2004 9:09 AM
To: [EMAIL PROTECTED]
Subject: Akamai DNS
Confirmed from 216.26.128.0/18, 69.2.192.0/19, and 206.196.0.0/20. Seems
to be using determinative destinations tho, as it works from some other
network sources. I'm guessing only certain bits of the network are under
attack or have failed for some reason, or that some parts are handling
On Tue, Jun 15, 2004 at 08:27:59AM -0500, Pranav Sheth wrote:
Seems to be the same thing here in DFW, Texas
Google is accessible and yahoo is not fully functional (login pages
fail).
Google pulled references for akamais dns servers a short period ago.
they are presently serving
, 216.239.51.104
Aliases: www.google.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Leo Bicknell
Sent: Tuesday, June 15, 2004 9:09 AM
To: [EMAIL PROTECTED]
Subject: Akamai DNS Issue?
x
--
Leo Bicknell - [EMAIL PROTECTED
, June 15, 2004 6:36 AM
To: [EMAIL PROTECTED]
Subject: Re: Akamai DNS Issue?
same here in El Salvador. Hope it doesn't take longer...
On 15 Jun 2004 at 9:08, Leo Bicknell wrote:
snip
From here neither www.google.com, nor www.apple.com work. Both
seem to return CNAMES to akadns.net addresses
Pranav Sheth wrote:
Seems to be the same thing here in DFW, Texas
Google is accessible and yahoo is not fully functional (login pages
fail).
Up here in Seattle, Google is working fine, but yahoo is broken. The
main yahoo.com page loads, but none of the subdomains I have tried are
resolvable.
] On
Behalf Of Leo Bicknell
Sent: Tuesday, June 15, 2004 9:09 AM
To: [EMAIL PROTECTED]
Subject: Akamai DNS Issue?
x
--
Leo Bicknell - [EMAIL PROTECTED] - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - [EMAIL PROTECTED], www.tmbg.org
People seem to be getting around this by changing their DNS entries.
E.g. www.yahoo.com always used to be a CNAME for www.yahoo.akadns.net. But
now:
# host www.yahoo.com
www.yahoo.com is an alias for www.dcn.yahoo.com.
www.dcn.yahoo.com has address 216.109.118.64
www.dcn.yahoo.com has
:[EMAIL PROTECTED]
Sent: Tuesday, June 15, 2004 9:09 AM
To: [EMAIL PROTECTED]
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
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 15, 2004 9:09 AM
To: [EMAIL PROTECTED]
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
--On Tuesday, June 15, 2004 12:59 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 didn't
So anyone know what was the cause ?
---Mike
At 09:08 AM 15/06/2004, Leo Bicknell wrote:
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
Mike Tancsa [EMAIL PROTECTED] 6/15/04 1:53:00 PM
So anyone know what was the cause ?
http://apnews.excite.com/article/20040615/D837KIU00.html
It appears that Akamai is claiming it was an international attack.
John
--
://www.theregister.co.uk/2004/06/15/akamai_goes_postal/
Brian Conant
Lead Security Engineer
ADESA Corp
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Mike Tancsa
Sent: Tuesday, June 15, 2004 2:53 PM
To: Leo Bicknell; [EMAIL PROTECTED]
Subject: Re: Akamai DNS Issue?
So
It appears that Akamai is claiming it was an international attack.
^ press and marketing departments
i imagine that the engineers, being prudent engineers, may still be
investigating
randy
Confirm here in China. mail.yahoo.com is not reachable.
I met this problem with www.toshiba.com about a month before, when www.toshiba.com
could only be resolved by using ATT's DNS server cache.
joe
Msg sent via Spymac Mail - http://www.spymac.com
On Tue, Jun 15, 2004 at 09:08:40AM -0400, Leo Bicknell wrote:
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
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 reported attack on the servers means that it doesn't matter how magic
50 matches
Mail list logo