- Original Message -
> From: "Michael Loftis via Outages"
> It's not just the local. 8.8.8.8 is caching the old entry still.
> Check the authoritative resolvers.
Point of order:
No "resolvers" are "authoritative". "Resolvers" (or, more fully, "Customer
resolver servers") are servers op
For future reference: https://developers.google.com/speed/public-dns/cache
will let you request a cache flush.
Damian
On Tue, Oct 7, 2014 at 2:46 PM, John Barbieri via Outages <
outages@outages.org> wrote:
> In the process of moving, these commands were all run within 5 seconds.
>
>
> jbarbieri
In the process of moving, these commands were all run within 5 seconds.
jbarbieri@jbarbieri-asus:~$ host heartbeat.belkin.com 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
heartbeat.belkin.com has address 54.163.74.132
heartbeat.belkin.com has address 54.163.87.225
hea
It looks to me, when querying Belkin's setup directly, they are
returning RR A records. (Please pay attention to the "QUESTION SECTION"
below, as it's going to become relevant):
$ dig @a.gtld-servers.net ns belkin.com.
;; QUESTION SECTION:
;belkin.com.IN NS
;; AUTHORITY
It's not just the local. 8.8.8.8 is caching the old entry still.
Check the authoritative resolvers.
On Tue, Oct 7, 2014 at 2:14 PM, Grant Ridder via Outages
wrote:
> Your large host list looks like it is just your local resolver.
>
> host heartbeat.belkin.com 8.8.8.8
>
> Using domain server:
>
>
http://tcrn.ch/1y30B6H
On Tue, Oct 7, 2014 at 2:23 PM, Chris Adams via Outages wrote:
> Once upon a time, Grant Ridder via Outages said:
> > Your large host list looks like it is just your local resolver.
>
> DNS records have been changed; it is now hosted on Amazon.
>
> $ dig +trace heartbea
Subject: Re: [outages] Belkin [heartbeat.belkin.com]
Your large host list looks like it is just your local resolver.
host heartbeat.belkin.com <http://heartbeat.belkin.com> 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
heartbeat.belkin.com
Once upon a time, Grant Ridder via Outages said:
> Your large host list looks like it is just your local resolver.
DNS records have been changed; it is now hosted on Amazon.
$ dig +trace heartbeat.belkin.com
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.23.rc1.el6_5.1 <<>> @c.root-servers.net
+trace hear
Your large host list looks like it is just your local resolver.
host heartbeat.belkin.com 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
heartbeat.belkin.com has address 67.20.176.130
On Tue, Oct 7, 2014 at 1:48 PM, Paul Miller via Outages wrote:
> On Tue, Oct 07,
I wish they added 127.0.0.1 to that list. =)
Frank
-Original Message-
From: Outages [mailto:outages-boun...@outages.org] On Behalf Of Paul Miller via
Outages
Sent: Tuesday, October 07, 2014 3:48 PM
To: outages@outages.org
Subject: Re: [outages] Belkin [heartbeat.belkin.com]
On Tue, Oct
On Tue, Oct 07, 2014 at 02:43:13PM -0400, Nick Olsen via Outages wrote:
> The current thought (Around the NOC here) is that DNS is breaking due to
> another user friendly feature. Where the router forwards you to it's config
> page automatically, if it thinks you have no internet..
I still don'
On 07 Oct 2014, at 19:57, Frank Bulk via Outages wrote:
> Why do that if Belkin is up and running again?
This thing seems to go down and up like a yoyo.
(I’m seeing it one hop behind 66.179.229.150 — works this very moment.)
Can’t get a reliable OS fingerprint (unless it’s an Airport Extreme…).
..@outages.org] *On Behalf Of *John
> Neiberger via Outages
> *Sent:* Tuesday, October 07, 2014 12:42 PM
> *To:* outages@outages.org
>
>
> *Subject:* Re: [outages] Belkin [heartbeat.belkin.com]
>
>
>
> Has anyone else tried the loopback/heartbeat workaroun
en
Network Operations (855) FLSPEED x106
From: "John Neiberger via Outages"
Sent: Tuesday, October 07, 2014 2:32 PM
To: "Frank Bulk"
Cc: "outages@outages.org"
Subject: Re: [outages] Belkin [heartbeat.belkin.com]
I jus
On Oct 8, 2014, at 12:57 AM, Frank Bulk via Outages wrote:
> Why do that if Belkin is up and running again?
So that it doesn't recur if things get dorked up, again? It's a great DDoS
vector - take down that IP, wedge every affected Belkin CPE on the Internet.
This kind of thing is extremely
;
>> *From:* Outages [mailto:outages-boun...@outages.org] *On Behalf Of *John
>> Neiberger via Outages
>> *Sent:* Tuesday, October 07, 2014 12:42 PM
>> *To:* outages@outages.org
>>
>> *Subject:* Re: [outages] Belkin [heartbeat.belkin.com]
>>
>>
>
day, October 07, 2014 12:42 PM
> *To:* outages@outages.org
>
> *Subject:* Re: [outages] Belkin [heartbeat.belkin.com]
>
>
>
> Has anyone else tried the loopback/heartbeat workaround with success? I've
> seen a few reports so far that this has temporarily solved the problem.
>
PM
To: Frank Bulk
Cc: outages@outages.org
Subject: Re: [outages] Belkin [heartbeat.belkin.com]
Given the number of current social media postings, it doesn't appear that they
are back up yet, but I suppose it is hard to say for sure given the number of
people affected. Twitter is all afl
>
>
>
> *From:* John Neiberger [mailto:jneiber...@gmail.com]
> *Sent:* Tuesday, October 07, 2014 1:01 PM
> *To:* Frank Bulk
> *Cc:* outages@outages.org
>
> *Subject:* Re: [outages] Belkin [heartbeat.belkin.com]
>
>
>
> Given the number of current social media postings, it
that
> Belkin doesn’t have it all worked out?
>
>
>
> Frank
>
>
>
> *From:* Outages [mailto:outages-boun...@outages.org] *On Behalf Of *John
> Neiberger via Outages
> *Sent:* Tuesday, October 07, 2014 12:42 PM
> *To:* outages@outages.org
>
> *Subject:* Re: [ou
..@outages.org] *On Behalf Of *John
>> Neiberger via Outages
>> *Sent:* Tuesday, October 07, 2014 11:04 AM
>> *To:* Josh Luthman
>> *Cc:* outages@outages.org; John Barbieri
>> *Subject:* Re: [outages] Belkin [heartbeat.belkin.com]
>>
>>
>>
: [outages] Belkin [heartbeat.belkin.com]
Has anyone else tried the loopback/heartbeat workaround with success? I've seen
a few reports so far that this has temporarily solved the problem.
John
On Tue, Oct 7, 2014 at 10:28 AM, Frank Bulk mailto:frnk...@iname.com> > wrote:
1:04 AM
> *To:* Josh Luthman
> *Cc:* outages@outages.org; John Barbieri
> *Subject:* Re: [outages] Belkin [heartbeat.belkin.com]
>
>
>
> I think it was initially suspected to be a firmware upgrade, but I doubt
> that's the case now. It's interesting to me that there are two
I just saw a forum post where Belkin recommended manually setting DNS to
see if that solves the problem. Putting all of this together, this is my
best guess as to what happened.
1. Routers regularly send heartbeat messages to heartbeat.belkin.com
2. Some routing failure causes quite a few netblock
, October 07, 2014 11:04 AM
To: Josh Luthman
Cc: outages@outages.org; John Barbieri
Subject: Re: [outages] Belkin [heartbeat.belkin.com]
I think it was initially suspected to be a firmware upgrade, but I doubt that's
the case now. It's interesting to me that there are two seemingly
DSLR:
http://www.dslreports.com/forum/r29585798-Belkin-Router-Owners-Take-Note.
And I am thinking the same thing you are. Doubt resi users upgraded
their router overnight.
Like you said, chances are it has to do with that heartbeat. Asked a few
folks around the US to ping it, some successful
I think it was initially suspected to be a firmware upgrade, but I doubt
that's the case now. It's interesting to me that there are two seemingly
unrelated fixes:
1. Put the IP for heartbeat.belkin.com on a loopback
2. Manually add working DNS entries to affected PCs
Reports indicate that either
67.20.176.130 to a pingable IP?
>
>
>
> Frank
>
>
>
> *From:* Outages [mailto:outages-boun...@outages.org] *On Behalf Of *Josh
> Luthman via Outages
> *Sent:* Tuesday, October 07, 2014 10:42 AM
> *To:* Paul Miller
> *Cc:* outages@outages.org
> *Subject:* Re: [outages] B
Miller
Cc: outages@outages.org
Subject: Re: [outages] Belkin [heartbeat.belkin.com]
Just because you can ping it does not mean it will work. I've confirmed with
other users this is the case. I believe there is some sort of HTTP request
that confirms the connection is working (like Wi
Where? I keep reading "bad firmware" problems but everything suggests
there is no automatic upgrade and I think we can safely assume resi users
didn't upgrade their routers over night.
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Tue, Oct 7,
Just because you can ping it does not mean it will work. I've confirmed
with other users this is the case. I believe there is some sort of HTTP
request that confirms the connection is working (like Windows, Android,
etc).
Another resolution is to just loopback 67.20.176.130 (seems to be this IP
Funny,
Just saw something about Belkin routers and a botched firmware upgrade.
I wonder if this is what they meant.
That being said, it is working fine from Zito Media in Clanton, AL.
--John
On 10/07/2014 10:17 AM, Paul Miller via Outages wrote:
On one of my netblocks my subscribers can nolon
On one of my netblocks my subscribers can nolonger ping Belkin. I can ping
heartbeat.belkin.com from my webservers and from subscriber units on a
different netblock.
Apparently Belkin routers ping the home base every couple seconds to determine
the correct color of the Internet light on the route
33 matches
Mail list logo
