IETF Logo Mail Archive

Re: [DNSOP] Using the SOA in a NXDOMAIN response (Was: [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dnsop-nxdomain-cut-00.txt]

"Wessels, Duane" <dwessels@verisign.com> Fri, 13 November 2015 21:04 UTC

Return-Path: <dwessels@verisign.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 728571B3192 for <dnsop@ietfa.amsl.com>; Fri, 13 Nov 2015 13:04:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level:
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_37=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0TTSpvc09tTf for <dnsop@ietfa.amsl.com>; Fri, 13 Nov 2015 13:04:01 -0800 (PST)
Received: from mail-oi0-x263.google.com (mail-oi0-x263.google.com [IPv6:2607:f8b0:4003:c06::263]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 056861B3181 for <dnsop@ietf.org>; Fri, 13 Nov 2015 13:03:54 -0800 (PST)
Received: by oies6 with SMTP id s6so7899068oie.1 for <dnsop@ietf.org>; Fri, 13 Nov 2015 13:03:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign_com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-type:content-id:content-transfer-encoding:mime-version; bh=9bF1QOiOJiR8KxA1kjjxFs+7irRV5/gOBGj8kEpuRWo=; b=R0M0qSO9YLkb+NkfdrH5Wn/VtnuE20c4Dj4ahHa3csLAS1ZiQ6Li9uLgwlRGDJZJms 9YHHkG3FonN01R0lr+2LGLRNQsHh0J9D12nHPJAVLXHwPkNSniTlcAQTBAWm0P80wUf1 bw3JycY1cZkXSkW0J79Llfy/FLsxGgP4aZstIemFqsl+XlBvjeqfa8SVGKAhfoLkwLnN uljZAKJK+/hb9sDq9aiCWLP6GMs0eWekhcRc6I8pzj/eZA/O8/fsfxl/V417eicfxu5C P1wpARgc7DyxOUFKA/u3ziUFzbxNdpahkY6lgtrYW22MrrRAEr9DDDQmE1XougzIhoew 63tw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:content-id:content-transfer-encoding :mime-version; bh=9bF1QOiOJiR8KxA1kjjxFs+7irRV5/gOBGj8kEpuRWo=; b=iAPvVIgBj+cLQTAFQ21zH6TNWQM5PCyPfwkrMDwO/7VT/tV/lz5q+4d+uRZrRsLs2C Jq+E6YzQOjXSRwqmLXfoDSEVtfGFlOFHaAbWlvqoQSqnP1YhkBbBegZgbtU70e5LdBWa ZUpJ3LjRQ+xhYTgaEikcBKjOrj768nJO4VjpNRCX5jf0oEuuZX5v5I6uQWwHWojMNSvv olXhTa26VjdN4MPeukSQoxUWIo6438mLmV7RSkiP2IHd27YPtPRP6dfCHlUtu35TEHjD EYfHke6FgmFSaNI4zPpZ5xmsYT5NfcKIwqs0eEI5edOLw1VdDwMaUVSe5p9aXGCQog8J AtPw==
X-Gm-Message-State: ALoCoQnGZVot2mg/EanAylUSB5664M39B6FMPTRGXi9Uh1G6yc+mTZIsSKIZ3XLH4iSr/R+IaphnuNZ1hTHHvr4fj0i0cXTang==
X-Received: by 10.55.25.31 with SMTP id k31mr24211691qkh.75.1447448634075; Fri, 13 Nov 2015 13:03:54 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id e7sm1783197qkj.7.2015.11.13.13.03.53 (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 13 Nov 2015 13:03:54 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id tADL3reb019391 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Nov 2015 16:03:53 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Fri, 13 Nov 2015 16:03:52 -0500
From: "Wessels, Duane" <dwessels@verisign.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Thread-Topic: Using the SOA in a NXDOMAIN response (Was: [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dnsop-nxdomain-cut-00.txt]
Thread-Index: AQHRHkzsLzgH0DcrgE2zKzLa0muCOp6axM+A
Date: Fri, 13 Nov 2015 21:03:52 +0000
Message-ID: <727FFD56-02B4-42D1-8EFC-D391F40FBFA1@verisign.com>
References: <20151106082238.GA2307@nic.fr> <A62EC834-C954-446C-9F7A-AB6D1F955C7F@verisign.com> <20151112081514.GA16017@laperouse.bortzmeyer.org> <39D878B4-9239-4983-8083-36BCA365BE62@verisign.com> <20151113195015.GB32106@sources.org>
In-Reply-To: <20151113195015.GB32106@sources.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <59795F92D7269449ABAF2C436B9AA3DF@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/YeIiSuEUtr1V5Kx5P2hHdGA0_cU>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] Using the SOA in a NXDOMAIN response (Was: [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dnsop-nxdomain-cut-00.txt]
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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>
X-List-Received-Date: Fri, 13 Nov 2015 21:04:02 -0000

> On Nov 13, 2015, at 11:50 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> 
> On Thu, Nov 12, 2015 at 06:13:04PM +0000,
> Wessels, Duane <dwessels@verisign.com> wrote 
> a message of 57 lines which said:
> 
>> As Mark pointed out, we can't use the SOA to make NXDOMAIN more aggressive.
>> 
>> For a name like foo.bar.example.com and an NXDOMAIN response from
>> example.com we can't assume that there would be a zone cut between
>> foo and bar.
> 
> Could anyone explain in detail why is it so? [I don't understand why
> the zone cut is important here: using the SOA does not depend on
> whether there is a zone cut or not.]
> 
> Let's say I query foo.bar.example to example's name servers. I get:
> 
> ...
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64182
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 8, ADDITIONAL: 1
> ...
> ;; QUESTION SECTION:
> ;foo.bar.example.		IN SOA
> ...
> 
> example.			5400 IN	SOA nsmaster.nic.example. hostmaster.nic.example. (
> 				2222956935 ; serial
> 				3600       ; refresh (1 hour)
>                                ....
> 
> It can mean only one thing, that bar.example does not exist. How could
> it be different?
> 

If 'bar.example IN A 127.0.0.1' existed in the example zone, what would you expect
for the response to your query above?

DW

v2.23.0 | Report a Bug | By Email