[27794] in North American Network Operators' Group
"Stale" root-server
daemon@ATHENA.MIT.EDU (Forrest W. Christian)
Tue Mar 14 00:22:50 2000
Date: Mon, 13 Mar 2000 22:17:32 -0700 (MST)
From: "Forrest W. Christian" <forrestc@iMach.com>
To: nanog@merit.edu
Message-ID: <Pine.BSF.4.21.0003132155340.24241-100000@workhorse.iMach.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
I just came across the fact that one of the root servers (G) has a stale
.com zone. (Serial number from 3/10). Of course, my primary DNS server
seems to prefer G (or any other root server with a problem for that
matter).
I did call the number for the NOC listed and let's just say that although
they said that "the responsible person would be notified" I got the
impression that fixing the problem wasn't going to be on the top of their
list and probably was going to wait till the next business day. I also
was told that "They got a call like this friday" (which was the last day
the data was synched.
Are there standards for operations of a root DNS server? I would think
that checking and making sure that your zone files are current would be
either something you could do once a day or at the minimum write a script
to check the serial against the current date and start yelping if it was
too far out of date.
If I was responsible for a root server, making sure it was up with the
"correct" (quotes added thanks to our favorite registry/ies) data would be
my top priority.
- Forrest W. Christian (forrestc@imach.com) KD7EHZ
----------------------------------------------------------------------
iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com
Solutions for your high-tech problems. (406)-442-6648
----------------------------------------------------------------------
