7 Oct
2014
7 Oct
'14
7:08 p.m.
On Tue, 07 Oct 2014 16:27:16 -0600, John Neiberger said:
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.
Seems like a dubious idea to equate "can't reach heartbeat server" with "not on the net at all". At the very least, I'd add a second clause "I have no reachable default route, and I must scream".