[outages] dns.com name servers down?

Jeremy Chadwick outages at jdc.parodius.com
Wed Jun 22 19:45:57 EDT 2011


Does anyone know geographically where the authoritative nameservers in
question were located?

The reason I ask: there was a fibre cut within XO's network near SF
(specifically 529 Bryant and Fremont) that correlates almost directly,
time-wise, with when Chris began seeing this problem.  Splicing took
about an hour.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                   Mountain View, CA, US |
| Making life hard for others since 1977.               PGP 4BD6C0CB |

On Wed, Jun 22, 2011 at 09:27:33AM -0700, Ray Sanders wrote:
> We're seeing some weird time-outs involving content coming from our
> CDN provider in LA,
> 
> Think there might be a larger issue at hand?
> 
> On Wed, Jun 22, 2011 at 9:09 AM, Frank Bulk <frnkblk at iname.com> wrote:
> > All I can add is that dns.com seems to be down from here (AS5056), too.
> >
> > Frank
> >
> > -----Original Message-----
> > From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
> > Behalf Of Chris Stone
> > Sent: Wednesday, June 22, 2011 9:59 AM
> > To: outages at outages.org
> > Subject: [outages] dns.com name servers down?
> >
> > Was trying to get to www.osdir.com this morning and dns queries were
> > failing. Investigating, seems that it's a result of an outage for dns.com -
> > am unable to get to any of their name servers, or their web site. Checking
> > mxtools.com, they concur that there's a problem:
> >
> > Error:
> > *osdir.com:mx* -ns1.dns.com: A connection attempt failed because the
> > connected party did not properly respond after a period of time, or
> > established connection failed because connected host has failed to respond
> > Reported by *mxtoolbox.com* on Wednesday, June 22, 2011 at 9:46:57 AM
> > (GMT-5)
> >
> >
> >
> > Error:
> > *osdir.com:mx* -ns4.dns.com: A connection attempt failed because the
> > connected party did not properly respond after a period of time, or
> > established connection failed because connected host has failed to respond
> > Reported by *mxtoolbox.com* on Wednesday, June 22, 2011 at 9:42:22 AM
> > (GMT-5)
> >
> >
> > Anyone heard about an outage there - for all their name servers from what I
> > am seeing?
> >
> >
> > Chris
> >
> >
> > _______________________________________________
> > Outages mailing list
> > Outages at outages.org
> > https://puck.nether.net/mailman/listinfo/outages
> >
> > _______________________________________________
> > Outages mailing list
> > Outages at outages.org
> > https://puck.nether.net/mailman/listinfo/outages
> >
> 
> 
> 
> -- 
> "Prediction is very difficult, especially about the future." -Niels Bohr
> --
> Ray Sanders
> Linux Administrator
> Village Voice Media
> Office: 602-744-6547
> Cell: 602-300-4344
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages



More information about the Outages mailing list