Re: Should a nameserver know about itself?

Mark.Andrews@nominum.com Fri, 01 June 2001 00:18 UTC

Received: from nic.cafax.se ([192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA10547 for <dnsop-archive@odin.ietf.org>; Thu, 31 May 2001 20:18:09 -0400 (EDT)
Received: by nic.cafax.se (8.12.0.Beta5/8.12.0.Beta5) id f51030Q8005161 for dnsop-outgoing; Fri, 1 Jun 2001 02:03:00 +0200 (MEST)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by nic.cafax.se (8.12.0.Beta7/8.12.0.Beta5) with ESMTP id f5102uLt005156 for <dnsop@cafax.se>; Fri, 1 Jun 2001 02:02:58 +0200 (MEST)
Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.11.3/8.11.2) with ESMTP id f5100bv05356; Fri, 1 Jun 2001 10:00:42 +1000 (EST) (envelope-from marka@nominum.com)
Message-Id: <200106010000.f5100bv05356@drugs.dv.isc.org>
To: Shane Kerr <shane@ripe.net>
Cc: Robert Elz <kre@munnari.OZ.AU>, dnsop@cafax.se
From: Mark.Andrews@nominum.com
Subject: Re: Should a nameserver know about itself?
In-reply-to: Your message of "Thu, 31 May 2001 12:29:09 +0200." <Pine.BSI.4.05L.10105311148580.26280-100000@x17.ripe.net>
Date: Fri, 01 Jun 2001 10:00:37 +1000
Sender: owner-dnsop@cafax.se
Precedence: bulk

> There is also the issue of educating administrators on this methodology,
> which isn't the way that most forward delegation is carried out (e.g.
> one of nominum.com's name servers is ns-ext.vix.com, which doesn't fit
> in the "use only name servers in the domain to respond authoritatively
> for that domain" model.

	As a model for good DNS delegation it is overkill.

	A just as robust model is "a nameserver should be a official
	(not stealth) server for the zone it lives in".  ns-ext.vix.com
	fits this model as it is a server for vix.com.

	This leads to NS chains of length 1.

	Mark
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews@nominum.com