Re: Should a nameserver know about itself?

Bill Woodcock <woody@zocalo.net> Wed, 09 May 2001 08:50 UTC

Received: from nic.cafax.se ([192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA02083 for <dnsop-archive@odin.ietf.org>; Wed, 9 May 2001 04:50:15 -0400 (EDT)
Received: by nic.cafax.se (8.12.0.Beta5/8.12.0.Beta5) id f498QtTP027466 for dnsop-outgoing; Wed, 9 May 2001 10:26:55 +0200 (MEST)
Received: from smtp1.zocalo.net (smtp1.zocalo.net [157.22.1.67]) by nic.cafax.se (8.12.0.Beta7/8.12.0.Beta5) with ESMTP id f498QsLt027461 for <dnsop@cafax.se>; Wed, 9 May 2001 10:26:54 +0200 (MEST)
Received: from secure (secure [157.22.1.13]) by smtp1.zocalo.net (8.9.1/8.9.1) with ESMTP id BAA06215; Wed, 9 May 2001 01:26:37 -0700 (PDT)
Date: Wed, 09 May 2001 01:26:36 -0700
From: Bill Woodcock <woody@zocalo.net>
To: Randy Bush <randy@psg.com>
cc: Bruce Campbell <bruce.campbell@apnic.net>, dnsop@cafax.se
Subject: Re: Should a nameserver know about itself?
In-Reply-To: <E14xO24-0003rl-00@rip.psg.com>
Message-ID: <Pine.GSO.4.21.0105090126170.22275-100000@secure.zocalo.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-dnsop@cafax.se
Precedence: bulk

      On Wed, 9 May 2001, Randy Bush wrote:

    > > Is the assumption that a nameserver should have information about itself
    > > correct?
    > no.  
    > analogy: i have phone directories in my house, but i happen not to have one
    > for the town in which my house is situated.

So, as an ignorant layer-2/layer-3 person stretching to understand
this layer-5 DNS stuff, lemme see if I can render that as an example
rather than an analogy:

APNIC delegates 2.0.0.0/16 to Foo-ISP:

    $ORIGIN 2.in-addr.arpa.
    0 IN SOA 0.2.in-addr.arpa root.apnic.net n n n n n
    IN NS ns.apnic.net.
    $ORIGIN 0.2.in-addr.arpa.
    0 IN NS ns2.foo-isp.net.

ns2.foo-isp.net has a zone file for 0.0.2.in-addr.arpa:

    $ORIGIN 0.2.in-addr.arpa.
    0 IN SOA 0.0.2.in-addr.arpa root.foo-isp.net n n n n n
      IN NS ns2.foo-isp.net.
    $ORIGIN 0.0.2.in-addr.arpa.
    0 IN PTR host0.foo-isp.net.
    1 IN PTR host1.foo-isp.net.
    254 IN PTR host254.foo-isp.net.
    255 IN PTR host255.foo-isp.net.

However, ns2.foo-isp.net's IP address is 1.0.2.1, and it isn't
authoritative for either the 2.0.1.in-addr.arpa. zone or the
foo-isp.net. zone, those are both held by ns1.foo-isp.net, whose IP
address is 1.0.1.1:

    $ORIGIN net.
    foo-isp IN SOA foo-isp.net root.foo-isp.net n n n n n
            IN NS ns1.foo-isp.net.
    $ORIGIN foo-isp.net.
    ns1 IN A 1.0.1.1
    ns2 IN A 1.0.2.1

    $ORIGIN 0.1.in-addr.arpa.
    1 IN SOA 1.0.1.in-addr.arpa root.foo-isp.net n n n n n
      IN NS ns1.foo-isp.net.
    2 IN SOA 2.0.1.in-addr.arpa root.foo-isp.net n n n n n
      IN NS ns1.foo-isp.net.
    $ORIGIN 1.0.1.in-addr.arpa.
    1 IN PTR ns1.foo-isp.net.
    $ORIGIN 2.0.1.in-addr.arpa.
    1 IN PTR ns2.foo-isp.net.

So ns1.foo-isp.net would know about itself, but ns2.foo-isp.net
would not know anything at all about itself beyond the fact that
"ns2.foo-isp.net" was the data of an NS record in its zone file.
Both would be properly configured.

Is that right?

                                -Bill