IETF Logo Mail Archive

Re: [Resolverless-dns] Load-balancing concerns

Jim Reid <jim@rfc1035.com> Thu, 08 November 2018 08:47 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: resolverless-dns@ietfa.amsl.com
Delivered-To: resolverless-dns@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCBC41293FB for <resolverless-dns@ietfa.amsl.com>; Thu, 8 Nov 2018 00:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=unavailable 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 M-72vh2krZyn for <resolverless-dns@ietfa.amsl.com>; Thu, 8 Nov 2018 00:47:28 -0800 (PST)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB761130E6C for <resolverless-dns@ietf.org>; Thu, 8 Nov 2018 00:47:26 -0800 (PST)
Received: from dhcp-8a2b.meeting.ietf.org (dhcp-8a2b.meeting.ietf.org [31.133.138.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 10BF82420FDE; Thu, 8 Nov 2018 08:47:23 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <CAN-AkJtKbgy0RNf6c5TZd3j5SsjaYe4CwtkaQzYA=FhrrAvJAA@mail.gmail.com>
Date: Thu, 08 Nov 2018 08:47:50 +0000
Cc: resolverless-dns@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <8849CBF3-1950-44BB-95C9-16F35F79E350@rfc1035.com>
References: <CAN-AkJtKbgy0RNf6c5TZd3j5SsjaYe4CwtkaQzYA=FhrrAvJAA@mail.gmail.com>
To: Justin Henck <henck=40google.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/resolverless-dns/f81CYebHTYlC1JNbRvYAsnkDSgk>
Subject: Re: [Resolverless-dns] Load-balancing concerns
X-BeenThere: resolverless-dns@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Resolverless DNS <resolverless-dns.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/resolverless-dns>, <mailto:resolverless-dns-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/resolverless-dns/>
List-Post: <mailto:resolverless-dns@ietf.org>
List-Help: <mailto:resolverless-dns-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/resolverless-dns>, <mailto:resolverless-dns-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Nov 2018 08:47:30 -0000


> On 8 Nov 2018, at 08:19, Justin Henck <henck=40google.com@dmarc.ietf.org> wrote:
> 
> You'll have to forgive my ignorance - I definitely don't pretend to be an expert in any of these areas.  My understanding (please correct me!) was that generally an authoritative will return a single A or AAAA record based on a particular query, but with DNSSEC it will return an entire relevant RRSET.

Not quite. If an authoritative server is queried for the A or AAAA records for some name, it will return all the matching A (or AAAA) records. [Modulo truncated responses and TCP retries.] It won't return a single A or AAAA record unless of course there's only one of them.

When DNSSEC is used, authoritative servers return RRsets.* That's because the signature covers the RRset and the validator has to have all of the original data -- the RRset -- so that it can validate the signed response.

*That's pretty much the same as the unsigned response with the addition of some extra RRtypes for the DNSSEC special sauce.

v2.23.0 | Report a Bug | By Email