[ On Tue, September 22, 1998 at 15:24:08 (-0500), Sean Donelan wrote: ]
Subject: Re: the GOV top-level domain
>GOV. was missing from A.ROOT-SERVERS.NET sometime yesterday, but the
>example with a timestampe has scrolled past my scroll buffer....
Apparently it is a "known" bug in bind that crops up from time
to time.
If they know about it you'd think it would take about a half hour or
less to write a wee script that could check and set of one of their many
network monitor alarms. They should be able to catch and fix such a
problem sooner than anyone can post to NANOG....
Date: Tue, 22 Sep 1998 19:41:15 -0400 (EDT)
From: "Greg A. Woods" <woods@most.weird.com>
Reply-To: nanog@merit.edu
To: nanog@merit.edu
Subject: Re: the GOV top-level domain
[ On Tue, September 22, 1998 at 15:24:08 (-0500), Sean Donelan wrote: ]
> Subject: Re: the GOV top-level domain
>
> >GOV. was missing from A.ROOT-SERVERS.NET sometime yesterday, but the
> >example with a timestampe has scrolled past my scroll buffer....
Hmm. I went back into the thread, but can't figure out what example
with the timestamp (what bug) is meant here. Someone care to explain?
Maybe I missed that message?
>
> Apparently it is a "known" bug in bind that crops up from time
> to time.
If they know about it you'd think it would take about a half hour or
less to write a wee script that could check and set of one of their many
network monitor alarms. They should be able to catch and fix such a
problem sooner than anyone can post to NANOG....
[ On Wed, September 23, 1998 at 08:59:12 (+0800), Mathias Koerber wrote: ]
Subject: Re: the GOV top-level domain
>GOV. was missing from A.ROOT-SERVERS.NET sometime yesterday, but the
>example with a timestampe has scrolled past my scroll buffer....
Hmm. I went back into the thread, but can't figure out what example
with the timestamp (what bug) is meant here. Someone care to explain?
Maybe I missed that message?
I did a query identical to the one I included in that message which did
show A.ROOT-SERVERS.NET as being lame for GOV., and since I have the
time of day in my shell prompt I'd have been able to confirm exactly
when it was lame, except example had scrolled beyond the end of my
xterm's scroll-back buffer.
If they know about it you'd think it would take about a half hour or
less to write a wee script that could check and set of one of their many
network monitor alarms. They should be able to catch and fix such a
problem sooner than anyone can post to NANOG....
We're NSI. We don't have to care.
-- With apologies to Lily Tomlin