IETF Logo Mail Archive

Re: [dnsext] Short introduction to zone cuts?

Doug Barton <dougb@dougbarton.us> Wed, 21 March 2012 05:48 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98EB021F84D7; Tue, 20 Mar 2012 22:48:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1332308932; bh=svsnDg7Iu/sw5UBOt7V7EuaFsMS07L8crTiE8S5K2JE=; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=KHx0TzJc0XoPOBwzqgETN25MSid/u9Zd2+yls9hqjnbm7v1GIt5aym72EBLvueUy6 SC603Fgn3hIQfCFKW1R0RhRwRb8kxC0K1vew+IBha22pmk3KDphPOqHCOCVI0lCROE 7blUdKsPpnq0hfobbq2Nu1zMw7XE+tfpt4holPKs=
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FB7F21F84D3 for <dnsext@ietfa.amsl.com>; Tue, 20 Mar 2012 22:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.655
X-Spam-Level:
X-Spam-Status: No, score=-3.655 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PNKN947vhDFs for <dnsext@ietfa.amsl.com>; Tue, 20 Mar 2012 22:48:51 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 56BE521F84D7 for <dnsext@ietf.org>; Tue, 20 Mar 2012 22:48:50 -0700 (PDT)
Received: (qmail 6166 invoked by uid 399); 21 Mar 2012 05:48:49 -0000
Received: from unknown (HELO ?172.17.198.245?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 21 Mar 2012 05:48:49 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F696BBE.8010209@dougbarton.us>
Date: Tue, 20 Mar 2012 22:48:46 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: Ray Bellis <Ray.Bellis@nominet.org.uk>
References: <946E9EC4-9872-4A98-BCEB-3CD7420929A1@vpnc.org> <20120316233618.16C831E9F8E3@drugs.dv.isc.org> <8D53F412-A917-4DB2-9B7F-527B8FDD6779@nominet.org.uk> <4F653C29.2070103@dougbarton.us> <B9ADF3A0-5943-4FFF-A614-5727D34AD6F6@nominet.org.uk> <4F67B7A7.1000608@dougbarton.us> <90DCCEAC-DBBF-423E-99DE-46D21D078F66@nominet.org.uk>
In-Reply-To: <90DCCEAC-DBBF-423E-99DE-46D21D078F66@nominet.org.uk>
X-Enigmail-Version: 1.4
Cc: DNSEXT Working Group <dnsext@ietf.org>
Subject: Re: [dnsext] Short introduction to zone cuts?
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

On 3/20/2012 2:31 AM, Ray Bellis wrote:
> 
> On 19 Mar 2012, at 22:48, Doug Barton wrote:
> 
>>
>> Right, and that's the devious subtlety of your message. :)  No one would
>> ever query ns1.example.com iteratively for the sample records in the
>> zone you posted because they would have no way of knowing that
>> ns1.example.com thought it was authoritative for those records.
> 
> Sure they would!

In your original post you posited something like this, if I understood
you correctly:

Parent:

$ORIGIN 4.3.2.1.foo.
8.7.6.5		NS	ns1.example.com.

ns1.example.com (child):

$ORIGIN 4.3.2.1.foo.
0.0.0.0		A	blah.example.com.
1.1.1.1		A	baz.example.com.

Under that scenario clients in the cloud would never query
ns1.example.com for 0.0.0.0.4.3.2.1.foo or 1.1.1.1.4.3.2.1.foo because
they'd have no delegation to it.

If I misunderstood, sorry for the noise.


Doug

-- 
    If you're never wrong, you're not trying hard enough
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext

v2.23.0 | Report a Bug | By Email