IETF Logo Mail Archive

Re: Should a nameserver know about itself?

James Raftery <james@now.ie> Thu, 10 May 2001 20:47 UTC

Received: from nic.cafax.se ([192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA08019 for <dnsop-archive@odin.ietf.org>; Thu, 10 May 2001 16:47:31 -0400 (EDT)
Received: by nic.cafax.se (8.12.0.Beta5/8.12.0.Beta5) id f4AKNkJT010843 for dnsop-outgoing; Thu, 10 May 2001 22:23:46 +0200 (MEST)
Received: from naptop.autonomica.se (flaptop.liman.sunet.se [193.10.90.102]) by nic.cafax.se (8.12.0.Beta7/8.12.0.Beta5) with ESMTP id f4AKNiLt010838 for <dnsop@cafax.se>; Thu, 10 May 2001 22:23:44 +0200 (MEST)
Received: by naptop.autonomica.se (8.12.0.Beta1/8.12.0.Beta1) id f4AKMDt6000515 for dnsop@cafax.se; Thu, 10 May 2001 22:22:13 +0200 (MEST)
Received: from romana.now.ie (romana.domainregistry.ie [193.1.142.6]) by nic.cafax.se (8.12.0.Beta7/8.12.0.Beta5) with SMTP id f4AAH8Lt006835 for <dnsop@cafax.se>; Thu, 10 May 2001 12:17:08 +0200 (MEST)
Received: (qmail 88928 invoked by uid 1001); 10 May 2001 09:17:07 -0000
Date: Thu, 10 May 2001 10:17:07 +0100
From: James Raftery <james@now.ie>
To: dnsop@cafax.se
Subject: Re: Should a nameserver know about itself?
Message-ID: <20010510101707.A88828@domainregistry.ie>
Mail-Followup-To: dnsop@cafax.se
References: <20010509150054.C84103@domainregistry.ie> <Pine.BSF.4.21.0105100927150.43413-100000@julubu.staff.apnic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.BSF.4.21.0105100927150.43413-100000@julubu.staff.apnic.net>; from bruce.campbell@apnic.net on Thu, May 10, 2001 at 09:50:26AM +1000
Sender: owner-dnsop@cafax.se
Precedence: bulk

On Thu, May 10, 2001 at 09:50:26AM +1000, Bruce Campbell wrote:
> Right.  Now that we've gotten that out of the way, can anyone suggest a
> *reliable* test for verifying that a nameserver is responding ( which is
> seperate from verifying that a nameserver is authoritatively serving a
> given zone )

They are two different tests, but they can both be implemented with a
query for the zone you're trying to delegate. If the server answers,
then it's responding. Then you perform a further check for aa bit, 
valid SOA RR or whatever you queried for.

tinydns, out-of-the-box, does not respond to queries for zones it is not
authoritative for. Unnecessarily seperating your tests for 
responsiveness and authority may be problematic because of this.


Regards,
james
-- 
James Raftery (JBR54)
  "It's somewhere in the Red Hat district"  --  A network engineer's
   freudian slip when talking about Amsterdam's nightlife at RIPE 38.

v2.23.0 | Report a Bug | By Email