Re: Should a nameserver know about itself?

Jim Reid <Jim.Reid@nominum.com> Thu, 10 May 2001 00:39 UTC

Received: from nic.cafax.se ([192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA29961 for <dnsop-archive@odin.ietf.org>; Wed, 9 May 2001 20:39:12 -0400 (EDT)
Received: by nic.cafax.se (8.12.0.Beta5/8.12.0.Beta5) id f4A0CmHA003797 for dnsop-outgoing; Thu, 10 May 2001 02:12:48 +0200 (MEST)
Received: from shell.nominum.com (shell.nominum.com [204.152.187.59]) by nic.cafax.se (8.12.0.Beta7/8.12.0.Beta5) with ESMTP id f4A0ClLt003792 for <dnsop@cafax.se>; Thu, 10 May 2001 02:12:48 +0200 (MEST)
Received: from shell.nominum.com (localhost [127.0.0.1]) by shell.nominum.com (Postfix) with ESMTP id EC38431914; Wed, 9 May 2001 17:12:17 -0700 (PDT)
To: Shane Kerr <shane@ripe.net>
Cc: dnsop@cafax.se
Subject: Re: Should a nameserver know about itself?
In-Reply-To: Message from Shane Kerr <shane@ripe.net> of "Thu, 10 May 2001 01:06:53 +0200." <Pine.BSI.4.05L.10105100101550.509-100000@kantoor.ripe.net>
Date: Wed, 09 May 2001 17:12:17 -0700
Message-ID: <24205.989453537@shell.nominum.com>
From: Jim Reid <Jim.Reid@nominum.com>
Sender: owner-dnsop@cafax.se
Precedence: bulk

>>>>> "Shane" == Shane Kerr <shane@ripe.net> writes:

    Shane> Okay, I'll bite.  What does it mean to have a PTR record in
    Shane> anything other than the in-addr.arpa tree?

It just means there's a PTR record in a zone outside the in-addr.arpa
tree. Whether that has any significance or not depends on whether
something knows to look for that PTR record. For instance a server
might come across it by following a CNAME when resolving a query. This
is how some folk implement simplified RFC2317 style reverse lookups.
Take a look at 6.242.6.62.in-addr.arpa for example.