Belkin Router issues this morning?

Tue Oct 7 22:32:24 UTC 2014

And this, my friends, is why friends don't let friends buy Belkin...

Apparently, you still can't fix stupid, no matter how hard you try.

-Mike

On Tuesday, October 7, 2014, John Neiberger <jneiberger at gmail.com> wrote:

> Sounds like it might have been a DNS issue of some sort. The end result was
> that the customer routers couldn't reach their heartbeat server, which made
> them think they weren't on the net. The routers would then be "helpful" and
> redirect all customer port 80 traffic to the router's configuration page to
> correct the "problem".
>
> It was a big mess that hopefully doesn't happen again. They've been making
> changes to their DNS this afternoon. Looks like they finally have it
> straightened out.
>
> John
>
> On Tue, Oct 7, 2014 at 10:05 AM, Steve Atkins <steve at blighty.com
> <javascript:;>> wrote:
>
> >
> > On Oct 7, 2014, at 8:34 AM, Justin Krejci <jkrejci at usinternet.com
> <javascript:;>> wrote:
> >
> > > https://twitter.com/search?q=%23belkin
> > >
> > > 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
> > ISPs, etc) there are no longer any issues for those devices, as reported
> by
> > several random people on the Internet.
> >
> > Over on outages, someone mentioned that heartbeat.belkin.com was
> > unreachable from some areas, and that was causing their routers to shut
> > down.
> >
> > Cheers,
> >   Steve
> >
> >
>

-- 
Mike Lyon
408-621-4826
mike.lyon at gmail.com

http://www.linkedin.com/in/mlyon