Re: Should a nameserver know about itself?
"Cricket Liu" <Cricket@verisign.com> Wed, 09 May 2001 23:54 UTC
Received: from nic.cafax.se ([192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA29505 for <dnsop-archive@odin.ietf.org>; Wed, 9 May 2001 19:54:57 -0400 (EDT)
Received: by nic.cafax.se (8.12.0.Beta5/8.12.0.Beta5) id f49NTjtP003594 for dnsop-outgoing; Thu, 10 May 2001 01:29:45 +0200 (MEST)
Received: from mail.acmebw.com ([208.206.240.75]) by nic.cafax.se (8.12.0.Beta7/8.12.0.Beta5) with ESMTP id f49NThLt003589 for <dnsop@cafax.se>; Thu, 10 May 2001 01:29:44 +0200 (MEST)
Received: from elsie (elsie.boulder.acmebw.com [206.168.194.124]) by mail.acmebw.com (Postfix) with SMTP id 3C77C101807; Wed, 9 May 2001 16:31:42 -0700 (PDT)
Message-ID: <081c01c0d8df$ecb47550$7cc2a8ce@elsie>
From: Cricket Liu <Cricket@verisign.com>
To: Shane Kerr <shane@ripe.net>, Robert Elz <kre@munnari.OZ.AU>
Cc: dnsop@cafax.se
References: <Pine.BSI.4.05L.10105100101550.509-100000@kantoor.ripe.net>
Subject: Re: Should a nameserver know about itself?
Date: Wed, 09 May 2001 17:29:41 -0600
Organization: VeriSign Global Registry Services
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-dnsop@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit
> > Any domain can have any RR in it. Any time you're tempted to > > generalise based upon domain name, you're almost invariably > > going to be wrong. > > Okay, I'll bite. What does it mean to have a PTR record in anything > other than the in-addr.arpa tree? While in some ways all domains are > equal, can't we at least say that some domains are more equal than > others? :P See RFC 2317, section 5.2. It suggests that, since you're already adding CNAME RRs to an in-addr.arpa zone, e.g., 1.0.168.192.in-addr.arpa. IN CNAME <something> why not make that <something> a domain name in a zone the delegate already owns, e.g., 1.0.168.192.in-addr.arpa. IN CNAME 1.0.customer.example. Then the customer adds 1.0.customer.example. IN PTR foo.customer.example. to his zone data file. Ergo, a PTR RR in what's traditionally considered a forward-mapping zone. cricket
- Re: Should a nameserver know about itself? Mats Dufberg
- Should a nameserver know about itself? Bruce Campbell
- Re: Should a nameserver know about itself? Randy Bush
- Re: Should a nameserver know about itself? bert hubert
- Re: Should a nameserver know about itself? Nathan Jones
- Re: Should a nameserver know about itself? Mark.Andrews
- Re: Should a nameserver know about itself? Mark.Andrews
- Re: Should a nameserver know about itself? Bill Woodcock
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itself? Mans Nilsson
- Re: Should a nameserver know about itself? Randy Bush
- Re: Should a nameserver know about itself? Mans Nilsson
- Re: Should a nameserver know about itself? Cathy Murphy
- Re: Should a nameserver know about itself? Cricket Liu
- Re: Should a nameserver know about itself? Kenneth Porter
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itself? Cathy Murphy
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itself? Bill Manning
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itself? Olaf Kolkman
- Re: Should a nameserver know about itself? itojun
- Re: Should a nameserver know about itself? James Raftery
- Re: Should a nameserver know about itself? Shane Kerr
- Re: Should a nameserver know about itself? Cricket Liu
- Re: Should a nameserver know about itself? Bruce Campbell
- Re: Should a nameserver know about itself? Jim Reid
- Re: Should a nameserver know about itself? Mark.Andrews
- Re: Should a nameserver know about itself? Mats Dufberg
- Re: Should a nameserver know about itself? bert hubert
- Re: Should a nameserver know about itself? Jim Reid
- Re: Should a nameserver know about itself? Peter Koch
- Re: Should a nameserver know about itself? Peter Koch
- Re: Should a nameserver know about itself? Sam Trenholme
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itself? Sam Trenholme
- Re: Should a nameserver know about itself? James Raftery
- Re: Should a nameserver know about itself? Bruce Campbell
- Re: Should a nameserver know about itself? Sam Trenholme
- Re: Should a nameserver know about itself? Mats Dufberg
- Re: Should a nameserver know about itself? Mans Nilsson
- Re: Should a nameserver know about itself? Jim Reid
- Re: Should a nameserver know about itself? Kenneth Porter
- Re: Should a nameserver know about itself? Mats Dufberg
- Checks performed during delegation. Bruce Campbell
- Re: Checks performed during delegation. Mats Dufberg
- Re: Should a nameserver know about itself? D. J. Bernstein
- Re: Should a nameserver know about itself? Shane Kerr
- Re: Should a nameserver know about itself? bert hubert
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itself? Bruce Campbell
- Re: Should a nameserver know about itself? Bill Manning
- Re: Should a nameserver know about itself? D. J. Bernstein
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itself? Shane Kerr
- Re: Should a nameserver know about itself? Mark.Andrews
- Re: Should a nameserver know about itself? George Michaelson
- Re: Should a nameserver know about itself? Bruce Campbell
- Re: Should a nameserver know about itself? D. J. Bernstein
- Re: Should a nameserver know about itself? James Raftery
- Re: draft-durand-ngtrans-dns-issues-00.txt Jim Reid
- Re: draft-durand-ngtrans-dns-issues-00.txt Robert Elz