[174990] in North American Network Operators' Group
Re: Belkin Router issues this morning?
daemon@ATHENA.MIT.EDU (Steven Parsons)
Tue Oct 7 18:39:35 2014
X-Original-To: nanog@nanog.org
Date: Tue, 07 Oct 2014 18:23:11 -0400
From: Steven Parsons <oz@columbus.rr.com>
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>,
Steve Atkins <steve@blighty.com>
In-Reply-To: <1B1E6AFB-CDE5-4182-AA3C-85A4BE1E0985@cable.comcast.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Looks like belkin=A9=F6s fix was to add different records.
DNS response this morning.
heartbeat.belkin.com. 4h14m31s IN A 67.20.176.130
DNS response this evening.
dig heartbeat.belkin.com +short
54.163.115.57
23.20.47.97
54.227.172.225
54.161.217.33
54.163.87.225
54.87.220.73
54.163.74.132
54.83.179.150
54.196.247.165
54.163.72.1
54.87.180.46
54.242.182.61
174.129.92.187
On 10/7/14, 5:54 PM, "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
wrote:
> Geesh. It was a tough day - lots of our customers with Belkin devices. Ag=
ree
> it has been fixable with customer changes but would have been better not =
to
> have to respond to this today (obviously).
>=20
> Regards,
> Jason=20
>=20
> Jason Livingood
> Comcast - Internet Services
>=20
>> On Oct 7, 2014, at 12:08, "Steve Atkins" <steve@blighty.com> wrote:
>> =20
>> =20
>>> On Oct 7, 2014, at 8:34 AM, Justin Krejci <jkrejci@usinternet.com> wro=
te:
>>> =20
>>> https://twitter.com/search?q=3D%23belkin
>>> =20
>>> Sounds like a bad firmware update most likely.
>>> Presumably the Belkin routers perform caching DNS for the LAN clients =
for
>>> if the LAN clients use alternate DNS servers (OpenDNS, Google, your ISP=
s,
>>> etc) there are no longer any issues for those devices, as reported by
>>> several random people on the Internet.
>> =20
>> Over on outages, someone mentioned that heartbeat.belkin.com was unreac=
hable
>> from some areas, and that was causing their routers to shut down.
>> =20
>> Cheers,
>> Steve
>> =20
>> =20
>=20
