IETF Logo Mail Archive

Re: [DNSOP] Why no more meta-queries? (Was: More work for DNSOP :-)

Shumon Huque <shuque@gmail.com> Tue, 10 March 2015 13:24 UTC

Return-Path: <shuque@gmail.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 5A2B11A886E for <dnsop@ietfa.amsl.com>; Tue, 10 Mar 2015 06:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 JCir4g98DXcb for <dnsop@ietfa.amsl.com>; Tue, 10 Mar 2015 06:24:48 -0700 (PDT)
Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (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 D0BEF1A00E0 for <dnsop@ietf.org>; Tue, 10 Mar 2015 06:24:47 -0700 (PDT)
Received: by qgdq107 with SMTP id q107so1612558qgd.7 for <dnsop@ietf.org>; Tue, 10 Mar 2015 06:24:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=9HRUQMHtvzM9nsWGyPEF4kFS+2slaOc6X4EJiJjarLM=; b=uWHDqaHjyyziJKokUUq6+bKWMy+vlQe3zTCHrCduKT4r6ymHHXfk9/cHOU/WvRgswe YrHVLLwNlvJ0cXaRZuxU+xgvXqsimU+7vFngRaP9Gc9GIkZvR9+WdUULqfIuwfp1U/SB l6j3TYG2XEZ7Lj/+EtNbbETq2e42bugkBzA5mXEdOXX0WmkFhwNlzp+1zDovjoWbDEN1 jkFWB0KHwA9amrOy/CjpmR8HBjX4erGGbRSFPeKexERTxcaqbbrOms2ygnKTO6s+u9Ci Uc0UzrlWDc+WiRcqHk9CoiGiqpEYTZsl8pBaxepUXKK6lmRw8tbnaLToqnNNF2R5dbgD Balw==
MIME-Version: 1.0
X-Received: by 10.55.52.83 with SMTP id b80mr2233497qka.36.1425993887192; Tue, 10 Mar 2015 06:24:47 -0700 (PDT)
Received: by 10.140.94.105 with HTTP; Tue, 10 Mar 2015 06:24:47 -0700 (PDT)
In-Reply-To: <54FED78F.8060501@nlnetlabs.nl>
References: <20150306145217.GA8959@nic.fr> <54F9C29E.9040408@jive.com> <54F9F90D.1020806@redbarn.org> <54F9FCD3.7010204@jive.com> <54F9FDFA.2030405@redbarn.org> <F25411A6-2CBD-4A76-949C-6E236FA87863@isoc.org> <20150306205920.GA17567@isc.org> <20150309142844.GA11602@nic.fr> <C1F43BD2-126F-4C1D-B084-A4B3A1F98ECD@nominet.org.uk> <CAHPuVdUyQWnRkvRhukHyCzZspUbj9iREyXSLmXTwmOy1m8DBTQ@mail.gmail.com> <20150309184507.GA7524@mycre.ws> <CAHPuVdXt2qFre9d8pW6KD9etbyFfAMgnycT_k4J9yNxCvoE_sw@mail.gmail.com> <CAHPuVdVzwcV48JMhRv0cxwRZFLiQnE6BrJrbVpn2yJExDGOCRA@mail.gmail.com> <54FED78F.8060501@nlnetlabs.nl>
Date: Tue, 10 Mar 2015 09:24:47 -0400
Message-ID: <CAHPuVdVhhEj5b1Qn=cxNY2dJkL4Vkd9cpdzuU78-CEAsJ_TRXA@mail.gmail.com>
From: Shumon Huque <shuque@gmail.com>
To: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
Content-Type: multipart/alternative; boundary="001a11490774191be80510ef13cf"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/vTfh8qKfVrZJeOKamSWV4Ir25r8>
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] Why no more meta-queries? (Was: More work for DNSOP :-)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: shuque@gmail.com
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: <http://www.ietf.org/mail-archive/web/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: Tue, 10 Mar 2015 13:24:49 -0000

On Tue, Mar 10, 2015 at 7:37 AM, W.C.A. Wijngaards <wouter@nlnetlabs.nl>
wrote:

>
> Unbound varies its answers depending on what the authority server is
> doing.  If the authority server inserts such an A or AAAA record in
> the additional section, unbound has code for this case (an AAAA
> inserted for an A query, or an A inserted for an AAAA query).
>

Ah, that's good to know. The code for this case is "insertion into the
resolver's cache" I presume.

What about the side facing the clients? Will unbound insert the gratuitous
A/AAAA in responses to them if they exist in cache? Quick tests I did
suggest not (yet).


> Only for the name that is queried, this to stop poisoning, and this is
> why the code is there (it is a (happy?) side-effect of anti-poison code).
>
>
Yup, that makes perfect sense. Thanks for the details Wouter!

Shumon Huque.

v2.23.0 | Report a Bug | By Email