[186073] in North American Network Operators' Group
Re: Bluehost.com
daemon@ATHENA.MIT.EDU (Stephane Bortzmeyer)
Wed Nov 25 13:05:15 2015
X-Original-To: nanog@nanog.org
Date: Wed, 25 Nov 2015 19:04:40 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: JoeSox <joesox@gmail.com>
In-Reply-To: <CAAXNyuCuQ_JRoOV1L2j1hWSu88gqyvZqHeV2bVDdwgR5thSzRg@mail.gmail.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Wed, Nov 25, 2015 at 08:41:55AM -0800,
JoeSox <joesox@gmail.com> wrote
a message of 9 lines which said:
> Anyone have the scope on the outage for Bluehost?
> https://twitter.com/search?q=%23bluehostdown&src=tyah
The two name servers ns1.bluehost.com and ns2.bluehost.com are awfully
slow to respond:
% check-soa -i picturemotion.com
ns1.bluehost.com.
74.220.195.31: OK: 2012092007 (1382 ms)
ns2.bluehost.com.
69.89.16.4: OK: 2012092007 (1388 ms)
As a result, most clients timeout.
May be a DoS against the name servers?
bluehost.com itself is DNS-hosted on a completely different
architecture. So it works fine. But the nginx Web site replies 502
Gateway timeout, probably overloaded by all the clients trying to get
informed.
The Twitter accounts of Bluehost do not distribute any useful
information.
