Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!decwrl!ucbvax!CS.WASHINGTON.EDU!yenbut
From: yenbut@CS.WASHINGTON.EDU
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re: Monitoring your nameserver
Message-ID: <9008172204.AA01398@hawk.cs.washington.edu>
Date: 17 Aug 90 22:04:44 GMT
References: <9008171554.AA08895@noc.net.yale.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 20

Alan S. Watt writes:
> So far, I haven't seen any nameserver failures which can still
> pass this test.

We have seen a problem at least once when only one domain name is
checked.  We used to check only a domain name at the top of our
authoritative zone, "CS.Washington.EDU", but one day
"Washington.EDU" which we do zone transfer from a campus
nameserver for some reasons quit working.

Now, we check both zones once a day (We depend on nameservers
backing up one another.  Our resolver code sends a query to one
nameserver at a time.  It waits a few seconds for an answer from
the first nameserver before sending the query to the second one.
We know almost right away when the first nameserver on a machine
we are using is down by a feeling of delay).  We don't check on
"1.0.0.127.in-addr.arpa".

   Voradesh Yenbut	<yenbut@cs.washington.edu>
   CSE Department, Univ of Washington, Seattle, WA