IETF Logo Mail Archive

Re: [DNSOP] CNAME chain length limits

dagon <dagon@sudo.sh> Thu, 28 May 2020 04:16 UTC

Return-Path: <dagon@sudo.sh>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A59E43A0BC6 for <dnsop@ietfa.amsl.com>; Wed, 27 May 2020 21:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.621
X-Spam-Level:
X-Spam-Status: No, score=-1.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.276, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 wF-Sn6SQ9ERw for <dnsop@ietfa.amsl.com>; Wed, 27 May 2020 21:16:05 -0700 (PDT)
Received: from sudo.sh (hexakaideca.sudo.sh [198.177.251.74]) by ietfa.amsl.com (Postfix) with ESMTP id 4FEAD3A0BC5 for <dnsop@ietf.org>; Wed, 27 May 2020 21:16:05 -0700 (PDT)
Received: by sudo.sh (Postfix, from userid 1000) id 6B1C8260251; Thu, 28 May 2020 04:16:03 +0000 (UTC)
Date: Thu, 28 May 2020 04:16:03 +0000
From: dagon <dagon@sudo.sh>
To: Mark Andrews <marka@isc.org>
Cc: Tony Finch <dot@dotat.at>, Evan Hunt <each@isc.org>, dnsop@ietf.org, John R Levine <johnl@taugh.com>
Message-ID: <20200528041603.GB7675@sudo.sh>
References: <alpine.OSX.2.22.407.2005271341530.35268@ary.qy> <20200527180846.GA51895@isc.org> <20200527200614.GC3582@sudo.sh> <alpine.DEB.2.20.2005280101240.18104@grey.csi.cam.ac.uk> <20200528024410.GA7675@sudo.sh> <14B0EB24-1A76-4976-9111-9F3D520B445C@isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <14B0EB24-1A76-4976-9111-9F3D520B445C@isc.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bEEH1fLnu9COvHhgaXIV7xW6VUA>
Subject: Re: [DNSOP] CNAME chain length limits
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 28 May 2020 04:16:07 -0000

On Thu, May 28, 2020 at 01:22:40PM +1000, Mark Andrews wrote:
> 'BAD (HORIZONTAL) REFERRAL' has nothing to do with CNAMES.  It’s reporting
> a referral to a set of servers that in turn return a referral to another
> set of servers server at the same depth.  It’s reported by ‘dig +trace’.

This thread sought ideas about what to measure in chain handling,
where one can encounter this error.  It's not CNAME-specific of
course, nor were the other NS-oriented comments, or resolution timing
limits, etc.

-- 
David Dagon
dagon@sudo.sh
D970 6D9E E500 E877 B1E3  D3F8 5937 48DC 0FDC E717

v2.23.0 | Report a Bug | By Email