16 Apr
2013
16 Apr
'13
2:50 p.m.
On 04/16/2013 01:58 PM, David Riley wrote:
Ah, no. There's almost nothing involving hosed DNS that involves rebooting
a nameserver. Nameservers are typically not Windows boxes. (standpoint: I
ran some of the largest nameservers on the enter network many years ago, and
I run some rather non-trivial ones now)
Well, unless your DNS server has crashed for some perfectly valid
reason. Say, maybe, the janitor bumped into the server rack and
accidentally ejected a hot-swap drive and caused a kernel panic.
I've heard of that happening (to companies who subsequently either
got rack doors or stopped letting the janitors clean the server
room).
Letting janitors in the server room is an unbelievably stupid thing to do
in the first place, and the downtime is what they had coming. I will (and
HAVE) clean the damn room myself before I'd let that happen.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
In this modern
day of pushing for everything to be web based, I am SO
frustrated by my hosting company being down for the last 9.5 hours due to a
DNS resolving issue. The old methods would never have had these problems..
That's not as bad as a provider trying to coverup and downplay a breach where
CCs were taken, I guess. It took them about that long to make a blog post
about it!
How do they have DNS issues for 9.5 hours? It should be as simple a fix as a
reboot of the DNS server in this case.