IETF Logo Mail Archive

RE: [Asrg] seeking comments on new RMX article

"Eric D. Williams" <eric@infobro.com> Tue, 06 May 2003 18:35 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02438 for <asrg-archive@odin.ietf.org>; Tue, 6 May 2003 14:35:38 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h46IiEs17222 for asrg-archive@odin.ietf.org; Tue, 6 May 2003 14:44:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46IiE817219 for <asrg-web-archive@optimus.ietf.org>; Tue, 6 May 2003 14:44:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02410; Tue, 6 May 2003 14:35:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D7JR-0001HB-00; Tue, 06 May 2003 14:37:13 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19D7JR-0001H8-00; Tue, 06 May 2003 14:37:13 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46If4817046; Tue, 6 May 2003 14:41:04 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46IeT817000 for <asrg@optimus.ietf.org>; Tue, 6 May 2003 14:40:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02279 for <asrg@ietf.org>; Tue, 6 May 2003 14:31:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D7Fo-0001FX-00 for asrg@ietf.org; Tue, 06 May 2003 14:33:28 -0400
Received: from black.infobro.com ([63.71.25.39] helo=infobro.com) by ietf-mx with smtp (Exim 4.12) id 19D7Fn-0001Ep-00 for asrg@ietf.org; Tue, 06 May 2003 14:33:28 -0400
Received: from red (unverified [207.199.136.153]) by infobro.com (EMWAC SMTPRS 0.83) with SMTP id <B0002399193@infobro.com>; Tue, 06 May 2003 14:33:02 -0400
Received: by localhost with Microsoft MAPI; Tue, 6 May 2003 14:33:09 -0400
Message-ID: <01C313DC.6A676640.eric@infobro.com>
From: "Eric D. Williams" <eric@infobro.com>
To: 'Vernon Schryver' <vjs@calcite.rhyolite.com>, "asrg@ietf.org" <asrg@ietf.org>
Subject: RE: [Asrg] seeking comments on new RMX article
Organization: Information Brokers, Inc.
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Tue, 06 May 2003 13:55:04 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I stand corrected.  I do not see that as a best practice (esp. related to 
secure configuration of an IP).

-e

On Tuesday, May 06, 2003 1:18 PM, Vernon Schryver 
[SMTP:vjs@calcite.rhyolite.com] wrote:
> > From: "Eric D. Williams" <eric@infobro.com>
>
> > ...
> > > That seems to be based on the mistaken notion that there can be only
> > > a single PTR RR per IP address.
> >
> > There can only be one canonical reverse mapping for an IP address.
>
> Where does the word "canonical" appear in RFC 1034 in connection with
> PTR RRs?
>
> >                                                                     There
> >                                                                     can
> > be multiple forward A records.  That is not to say the a PTR record can't 
be
> >
> > dynamically configured. However, yes that is the case for any instance for 
a
> >
> > transient or permenant assignment of a PTR RR AFAIK.
> >
> > 100	IN	PTR	domain1.com.
> > 	IN	PTR	domain2.com.
> >
> > does not work AFAIK, I will give it a shot.
>
> Those are quite similar to the lines that temporarily cause this:
>     % nslookup -d 192.188.61.4
>     ...
> 	QUESTIONS:
> 	    4.61.188.192.in-addr.arpa, type = PTR, class = IN
> 	ANSWERS:
> 	->  4.61.188.192.in-addr.arpa
> 	    name = andesite.rhyolite.com
> 	    ttl = 86400 (1D)
> 	->  4.61.188.192.in-addr.arpa
> 	    name = ns3.rhyolite.com
> 	    ttl = 86400 (1D)
>     ...
>
>
> See also http://www.google.com/search?q=%22multiple+ptr%22+dns
>
>
> Vernon Schryver    vjs@rhyolite.com
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg

_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg

v2.23.0 | Report a Bug | By Email