16 Apr
2013
16 Apr
'13
12:09 p.m.
On 04/16/2013 01:58 PM, David Riley wrote:
On Apr 16, 2013, at 1:37 PM, Dave McGuire <mcguire at neurotica.com> wrote:
I was assuming it was a non-trivial fault. I'm used to DNS servers not
failing I guess. ;)
My home DNS server crashed when my CD-ROM drive failed once...kept
running until I tried to update the zonefile.
HOW DOES A CD-ROM DRIVE SPONTANEOUSLY FAIL?!
On 04/16/2013 12:19 PM, Cory Smelosky 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). 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.
- Dave
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Experiments