Looks like belkin¹s 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. Agree it has been fixable with customer changes but would have been better not to have to respond to this today (obviously).
Regards, Jason
Jason Livingood Comcast - Internet Services
On Oct 7, 2014, at 12:08, "Steve Atkins" <steve@blighty.com> wrote:
On Oct 7, 2014, at 8:34 AM, Justin Krejci <jkrejci@usinternet.com> 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