IETF Logo Mail Archive

Re: [DNSOP] WGLC: "Considerations for the use of DNS Reverse Mapping"

bmanning@vacation.karoshi.com Mon, 31 March 2008 20:29 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 B3AAF28C3D9; Mon, 31 Mar 2008 13:29:22 -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 B56793A6967 for <dnsop@core3.amsl.com>; Mon, 31 Mar 2008 13:29:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ctAq-Dzj4nKb for <dnsop@core3.amsl.com>; Mon, 31 Mar 2008 13:29:15 -0700 (PDT)
Received: from vacation.karoshi.com (unknown [IPv6:2002:c620:68b:0:230:48ff:fe11:220a]) by core3.amsl.com (Postfix) with ESMTP id F142D3A6AED for <dnsop@ietf.org>; Mon, 31 Mar 2008 13:29:13 -0700 (PDT)
Received: from karoshi.com (localhost.localdomain [127.0.0.1]) by vacation.karoshi.com (8.12.8/8.12.8) with ESMTP id m2VKRRWG032600; Mon, 31 Mar 2008 20:27:27 GMT
Received: (from bmanning@localhost) by karoshi.com (8.12.8/8.12.8/Submit) id m2VKRDuD032592; Mon, 31 Mar 2008 20:27:13 GMT
Date: Mon, 31 Mar 2008 20:27:13 +0000
From: bmanning@vacation.karoshi.com
To: Mark Andrews <Mark_Andrews@isc.org>
Message-ID: <20080331202713.GB32510@vacation.karoshi.com.>
References: <a06240801c416cbfb5028@[10.31.68.58]> <200803311934.m2VJYcjk072082@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <200803311934.m2VJYcjk072082@drugs.dv.isc.org>
User-Agent: Mutt/1.4.1i
Cc: IETF DNSOP WG <dnsop@ietf.org>, bmanning@vacation.karoshi.com, Edward Lewis <Ed.Lewis@neustar.biz>, Peter Koch <pk@DENIC.DE>
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

On Tue, Apr 01, 2008 at 06:34:38AM +1100, Mark Andrews wrote:
> 
> 	Multiple PTR records do not scale.

	what does that mean Mark?
	
	why does "Multiple A records" scale and not others?
	is this a DNS protocol issue or an implementation artifact?


> 	Today we have reverse lookups that fail because people
> 	followed this path and exceeded the 64K DNS message size
> 	of TCP.

	and the same failure would be true for multiple instances
	of any RR type. 

> 	When people have a 100 thousand virtual domains on a 
> 	box you just can't have PTR records for all of them.

	and apparently you can't have A records for them either.

> 
> 	Mark

	so the actual spec limit is any mixture of RR types that
	will fit into a 64k DNS message on TCP.  Right?

--bill
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

v2.23.0 | Report a Bug | By Email