Re: Multiple PTR records

Shane Kerr <shane@ripe.net> Fri, 08 June 2001 09:22 UTC

Received: from nic.cafax.se (nic.cafax.se [192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA07966 for <dnsop-archive@odin.ietf.org>; Fri, 8 Jun 2001 05:22:06 -0400 (EDT)
Received: by nic.cafax.se (8.12.0.Beta5/8.12.0.Beta5) id f588lxsB016731 for dnsop-outgoing; Fri, 8 Jun 2001 10:47:59 +0200 (MEST)
Received: from penguin.ripe.net (penguin.ripe.net [193.0.1.232]) by nic.cafax.se (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f588lvuA016726 for <dnsop@cafax.se>; Fri, 8 Jun 2001 10:47:57 +0200 (MEST)
Received: (from shane@localhost) by penguin.ripe.net (8.10.2/8.10.2) id f588lm317222; Fri, 8 Jun 2001 10:47:48 +0200
Date: Fri, 08 Jun 2001 10:47:48 +0200
From: Shane Kerr <shane@ripe.net>
To: Kevin Darcy <kcd@daimlerchrysler.com>
Cc: dnsop@cafax.se, comp-protocols-dns-bind@moderators.isc.org
Subject: Re: Multiple PTR records
Message-ID: <20010608104746.B17160@penguin.ripe.net>
References: <200106072259.f57MxFv91665@drugs.dv.isc.org> <3B201B46.97FDF5A4@daimlerchrysler.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3B201B46.97FDF5A4@daimlerchrysler.com>; from kcd@daimlerchrysler.com at 2001-06-07 20:24:38 +0000
Sender: owner-dnsop@cafax.se
Precedence: bulk

On 2001-06-07 20:24:38 +0000, Kevin Darcy wrote:
> 
> I wonder if this would be good BCP material (?). RFC 2181 (not a BCP
> of course but Standards Track) almost seems to *encourage* multiple
> PTRs by "clarifying" that it is supported in the protocol. Now that
> the cat is out of the bag, perhaps there should be a BCP stating that,
> while multiple PTRs are technically possible, they are generally
> undesirable and when taken to extremes can in fact cause problems.
> 
> I would not volunteer to write such a document, of course, given my
> even-more-radical view that reverse DNS should probably go away or its
> use be severely limited (and I don't think keeping reverse DNS around
> solely as a sort of "ISP intelligence test" is really a strong
> argument, even when couched in terms of spam-prevention).

This is an intriguing idea.  To be honest, at first glance it doesn't
seem *too* radical to me.  I mean, what's the real "use case" for
referse DNS?  Certainly any "match forward/reverse" for "security" has
long been discredited.  The ability to put a machine name in my utmp
entry seems like a very small gain for such a large system.

OTOH, my understanding of the IPv6 world is, "yes IPv6 numbers are
totally ridiculous, so use DNS for everything".  In such a world,
reverse DNS seems to take on a huge importance.  Not that I've heard any
proposals how ISP's are going to manage running reverse DNS for the /48
they're going to have to give out to each dial-up customer.  (I'm sure
that somebody has a clever solution for this, I just haven't heard it.)

-- 
Shane