Re: [DNSOP] WGLC: "Considerations for the use of DNS Reverse Mapping"
Andrew Sullivan <ajs@commandprompt.com> Tue, 01 April 2008 21:36 UTC
Return-Path: <dnsop-bounces@ietf.org>
X-Original-To: dnsop-archive@lists.ietf.org
Delivered-To: ietfarch-dnsop-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E4C928C1D3; Tue, 1 Apr 2008 14:36:09 -0700 (PDT)
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 560B728C132 for <dnsop@core3.amsl.com>; Tue, 1 Apr 2008 14:36:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level:
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A5eFqywX15P3 for <dnsop@core3.amsl.com>; Tue, 1 Apr 2008 14:36:07 -0700 (PDT)
Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by core3.amsl.com (Postfix) with ESMTP id 6A20028C194 for <dnsop@ietf.org>; Tue, 1 Apr 2008 14:36:07 -0700 (PDT)
Received: from commandprompt.com (CPE0012170bc0fe-CM0012c90ce996.cpe.net.cable.rogers.com [99.230.253.189]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m31LacQg005145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Tue, 1 Apr 2008 14:36:40 -0700
Date: Tue, 01 Apr 2008 17:36:02 -0400
From: Andrew Sullivan <ajs@commandprompt.com>
To: dnsop@ietf.org
Message-ID: <20080401213559.GA38207@commandprompt.com>
References: <200803312055.m2VKtQvt039221@drugs.dv.isc.org> <a06240801c417f486db4d@[192.168.1.100]>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <a06240801c417f486db4d@[192.168.1.100]>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Tue, 01 Apr 2008 14:36:41 -0700 (PDT)
Subject: Re: [DNSOP] WGLC: "Considerations for the use of DNS Reverse Mapping"
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsop-bounces@ietf.org
Errors-To: dnsop-bounces@ietf.org
Dear colleagues, On Tue, Apr 01, 2008 at 10:36:28AM -0400, Edward Lewis wrote: > Multiple PTR records can be stored in a single PTR RRset. If a > device at an IP address (v4 or v6) has multiple identities with > domain names, it would be good to have a PTR for each. However, this > is not always practical. In some operational situations, an address > may have thousands of domain names holding an address record (A or > AAAA) with the address as the value. > > The number of address records in an PTR set before tripping the upper > limit on what can fit on even a TCP carried DNS message is > approximately 4000 for A RR only and about 2000 for AAAA RR only. > > If an address has just a few corresponding forward map records, it is > worth entering them all. If an address has many, a better strategy > is to enter a few as is needed, adding more only when there is an > operational request. I'm inclined to add this text. I'd like additional expressions of support (or edits, or whatever) from the WG to confirm my inclination. Thanks, A -- Andrew Sullivan ajs@commandprompt.com +1 503 667 4564 x104 http://www.commandprompt.com/ _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/liFrom dnsop-bounces@ietf.org Tue Apr 1 14:36:09 2008 Return-Path: <dnsop-bounces@ietf.org> X-Original-To: dnsop-archive@optimus.ietf.org Delivered-To: ietfarch-dnsop-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E4C928C1D3; Tue, 1 Apr 2008 14:36:09 -0700 (PDT) X-Original-To: dnsop@core3.amsl.com Delivered-To: dnsop@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 560B728C132 for <dnsop@core3.amsl.com>; Tue, 1 Apr 2008 14:36:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.735 X-Spam-Level: X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A5eFqywX15P3 for <dnsop@core3.amsl.com>; Tue, 1 Apr 2008 14:36:07 -0700 (PDT) Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by core3.amsl.com (Postfix) with ESMTP id 6A20028C194 for <dnsop@ietf.org>; Tue, 1 Apr 2008 14:36:07 -0700 (PDT) Received: from commandprompt.com (CPE0012170bc0fe-CM0012c90ce996.cpe.net.cable.rogers.com [99.230.253.189]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m31LacQg005145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Tue, 1 Apr 2008 14:36:40 -0700 Date: Tue, 1 Apr 2008 17:36:02 -0400 From: Andrew Sullivan <ajs@commandprompt.com> To: dnsop@ietf.org Message-ID: <20080401213559.GA38207@commandprompt.com> References: <200803312055.m2VKtQvt039221@drugs.dv.isc.org> <a06240801c417f486db4d@[192.168.1.100]> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <a06240801c417f486db4d@[192.168.1.100]> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Tue, 01 Apr 2008 14:36:41 -0700 (PDT) Subject: Re: [DNSOP] WGLC: "Considerations for the use of DNS Reverse Mapping" X-BeenThere: dnsop@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe> List-Archive: <http://www.ietf.org/pipermail/dnsop> List-Post: <mailto:dnsop@ietf.org> List-Help: <mailto:dnsop-request@ietf.org?subject=help> List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: dnsop-bounces@ietf.org Errors-To: dnsop-bounces@ietf.org Dear colleagues, On Tue, Apr 01, 2008 at 10:36:28AM -0400, Edward Lewis wrote: > Multiple PTR records can be stored in a single PTR RRset. If a > device at an IP address (v4 or v6) has multiple identities with > domain names, it would be good to have a PTR for each. However, this > is not always practical. In some operational situations, an address > may have thousands of domain names holding an address record (A or > AAAA) with the address as the value. > > The number of address records in an PTR set before tripping the upper > limit on what can fit on even a TCP carried DNS message is > approximately 4000 for A RR only and about 2000 for AAAA RR only. > > If an address has just a few corresponding forward map records, it is > worth entering them all. If an address has many, a better strategy > is to enter a few as is needed, adding more only when there is an > operational request. I'm inclined to add this text. I'd like additional expressions of support (or edits, or whatever) from the WG to confirm my inclination. Thanks, A -- Andrew Sullivan ajs@commandprompt.com +1 503 667 4564 x104 http://www.commandprompt.com/ _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/stinfo/dnsop listinfo/dnsop
- [DNSOP] WGLC: "Considerations for the use of DNS … Peter Koch
- Re: [DNSOP] WGLC: "Considerations for the use of … Brian Dickson
- Re: [DNSOP] WGLC: "Considerations for the use of … Dean Anderson
- Re: [DNSOP] WGLC: "Considerations for the use of … Stephane Bortzmeyer
- Re: [DNSOP] WGLC: "Considerations for the use of … Andras Salamon
- Re: [DNSOP] WGLC: "Considerations for the use of … JINMEI Tatuya / 神明達哉
- Re: [DNSOP] WGLC: "Considerations for the use of … JINMEI Tatuya / 神明達哉
- Re: [DNSOP] WGLC: "Considerations for the use of … Paul Wouters
- Re: [DNSOP] WGLC: "Considerations for the use of … JINMEI Tatuya / 神明達哉
- Re: [DNSOP] WGLC: "Considerations for the use of … Brian Dickson
- Re: [DNSOP] WGLC: "Considerations for the use of … Andrew Sullivan
- Re: [DNSOP] WGLC: "Considerations for the use of … Brian Dickson
- Re: [DNSOP] WGLC: "Considerations for the use of … Robert Story
- Re: [DNSOP] WGLC: "Considerations for the use of … bmanning
- Re: [DNSOP] WGLC: "Considerations for the use of … Andrew Sullivan
- Re: [DNSOP] WGLC: "Considerations for the use of … Andrew Sullivan
- Re: [DNSOP] WGLC: "Considerations for the use of … Edward Lewis
- Re: [DNSOP] WGLC: "Considerations for the use of … Mark Andrews
- Re: [DNSOP] WGLC: "Considerations for the use of … bmanning
- Re: [DNSOP] WGLC: "Considerations for the use of … Mark Andrews
- Re: [DNSOP] WGLC: "Considerations for the use of … Andrew Sullivan
- Re: [DNSOP] WGLC: "Considerations for the use of … Edward Lewis
- Re: [DNSOP] WGLC: "Considerations for the use of … Andrew Sullivan
- Re: [DNSOP] WGLC: "Considerations for the use of … Ted Lemon
- Re: [DNSOP] WGLC: "Considerations for the use of … Joe Abley
- Re: [DNSOP] WGLC: "Considerations for the use of … JINMEI Tatuya / 神明達哉
- Re: [DNSOP] WGLC: "Considerations for the use of … Andrew Sullivan
- Re: [DNSOP] WGLC: "Considerations for the use of … JINMEI Tatuya / 神明達哉
- Re: [DNSOP] WGLC: "Considerations for the use of … Samuel Weiler
- Re: [DNSOP] WGLC: "Considerations for the use of … JINMEI Tatuya / 神明達哉
- Re: [DNSOP] WGLC: "Considerations for the use of … JINMEI Tatuya / 神明達哉
- [DNSOP] Issue 22, unfairness (was: WGLC: "Conside… Andrew Sullivan
- Re: [DNSOP] WGLC: "Considerations for the use of … Andrew Sullivan
- Re: [DNSOP] WGLC: "Considerations for the use of … Andrew Sullivan
- Re: [DNSOP] WGLC: "Considerations for the use of … Stephane Bortzmeyer
- Re: [DNSOP] WGLC: "Considerations for the use of … Dean Anderson
- Re: [DNSOP] WGLC: "Considerations for the use of … bill fumerola
- Re: [DNSOP] WGLC: "Considerations for the use of … Andrew Sullivan