[outages] New York Times and corporate web site down

[Jeremy Chadwick]

Follow-up to this, which I just found out about today:

First, this Wild Wacky Action Bike of sorts (note what site posted it
and hold that thought):

http://www.washingtonpost.com/blogs/compost/wp/2013/08/14/new-york-times-web-site-goes-down-panicked-mobs-stream-into-street-demanding-to-know-the-trends/

...which was later debunked -- turns out the NYT was doing maintenance
of some sort which broke stuff (brings into question why they were doing
this during peak morning hours):

http://www.nytimes.com/2013/08/15/business/media/new-york-times-web-site-returns-after-hours-offline.html?_r=0

And further analysis of some sort:

http://www.zdnet.com/what-happened-to-the-new-york-times-website-7000019453/

And now the irony:

http://news.slashdot.org/story/13/08/15/162211/washington-post-hacked-a-day-after-new-york-times

-- 
| Jeremy Chadwick                                   jdc at koitsu.org |
| UNIX Systems Administrator                http://jdc.koitsu.org/ |
| Making life hard for others since 1977.             PGP 4BD6C0CB |

On Wed, Aug 14, 2013 at 09:43:36AM -0700, Jeremy Chadwick wrote:
> On Wed, Aug 14, 2013 at 12:27:48PM -0400, Edward Vielmetti wrote:
> > Reports filtering in from Twitter say that
> >    http://www.nytimes.com
> > and
> >    http://www.nytco.com
> > are unreachable.
> > 
> > I'm getting a DNS failure from "dig".
> > 
> > emv$ dig nytimes.com
> > 
> > ; <<>> DiG 9.6-ESV-R4-P3 <<>> nytimes.com
> > ;; global options: +cmd
> > ;; connection timed out; no servers could be reached
> > 
> > and DNS check at
> > 
> > http://dnscheck.se/log.pl?domain=nytimes.com&date=last
> > 
> > reports a problem with 'ns1t.nytimes.com'.
> 
> I don't know where you got that FQDN from.  The log doesn't mention any
> such FQDN.  The log reports A record lookup failures for
> dns.ewr1.nytimes.com.  And I can confirm thAt problem.
> 
> Per a.gtld-servers.net:
> 
> ;; AUTHORITY SECTION:
> nytimes.com.            172800  IN      NS      dns.sea1.nytimes.com.
> nytimes.com.            172800  IN      NS      dns.ewr1.nytimes.com.
> 
> ;; ADDITIONAL SECTION:
> dns.sea1.nytimes.com.   172800  IN      A       170.149.173.133
> dns.ewr1.nytimes.com.   172800  IN      A       170.149.168.134
> 
> Neither 170.149.173.133 or 170.149.168.134 are responding to queries (A
> records for www.nytimes.com, NS records for sea1.nytimes.com or
> ewr1.nytimes.com (not sure if there are any), A records for the
> aforementioned FQDNs, etc.).  Or the response may be spotty -- I did not
> try more than a couple times.
> 
> Both IPs respond to ICMP ECHO, so if resolution isn't working, the
> possibilities/reasons why are almost endless.  Rather not speculate.
> 
> -- 
> | Jeremy Chadwick                                   jdc at koitsu.org |
> | UNIX Systems Administrator                http://jdc.koitsu.org/ |
> | Making life hard for others since 1977.             PGP 4BD6C0CB |
> 
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages