IETF Logo Mail Archive

Re: [DNSOP] Why would a v4 client send AAAA query?

Töma Gavrichenkov <ximaera@gmail.com> Thu, 29 August 2019 12:22 UTC

Return-Path: <ximaera@gmail.com>
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 187E91200F3 for <dnsop@ietfa.amsl.com>; Thu, 29 Aug 2019 05:22:04 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 55sa832iBIHL for <dnsop@ietfa.amsl.com>; Thu, 29 Aug 2019 05:22:02 -0700 (PDT)
Received: from mail-yw1-xc33.google.com (mail-yw1-xc33.google.com [IPv6:2607:f8b0:4864:20::c33]) (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 B8FD11200D5 for <dnsop@ietf.org>; Thu, 29 Aug 2019 05:22:02 -0700 (PDT)
Received: by mail-yw1-xc33.google.com with SMTP id n126so1063139ywf.1 for <dnsop@ietf.org>; Thu, 29 Aug 2019 05:22:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=p+yRASzx1w6BWw7cWWFzZMhaU3vxGstnfyFeKCesomU=; b=nPi5sAEdG5gpn2sbLggeksfDB5FaXJrbKTPLk+pUn9Ck2pumrs7Ich6AX4rJD4LuhK wGdrs8KQMx73mMJQxAVSOCQ4RJ6o6p2RF5U+WxH9eeSShjRdDazdmJ7REKyIHP827pW6 vIdRb4NrGFh1LOLN0VecULi/bVjs5U4OaWy9QFOJNxSa69gBk/BRs9UKvQ+prC22MMgk MrC3wm06XHvnnvDVxYQn1cFOgNlJvO4qEYkGkQaG67iVyt4uKKPEG2Q97ojOnHk8eNhI K4pH3XC0e4bqd+BqRTgoLmgwa/4RjqvLxFbL6k5CZLyBY+HSRHaQ8oHoR1S7IKEYazR8 aTDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=p+yRASzx1w6BWw7cWWFzZMhaU3vxGstnfyFeKCesomU=; b=hDnMC2xZPXyQTawWQ8FcLvr5BCSjqbCvVEDw1SgoKFc5tXBrTG7ytu9fEjwiXr3A3m 7Glpp85qP1AAHlfoC/bD3QDrnL3m25W57c8D4IyWK4xBsHMXqEC5PRI/3HnbL/l+WVFG BN7FoIDc/RobgfzbhC2/etztvX3qcFXGIl10draOPzswXrPDLqnYNNUKxGG3FeTI6wkh UPspd65DpTqOr7sjdLBfL8RR2rCCCcm0MbnfUDzU8tKzOdag7O0DdwJthy4RQzdJDWYY 5uk9VvU/XKytB4DOP+ia+Vwyb3k0ND83KdbSiy/AZsmWIJMzOzBjZqXRYgFWU1PbR+DM s8tA==
X-Gm-Message-State: APjAAAXseH+qCRvgV735CEY2sWOiO+oYr+0mRfI7MBIwSZzM1zL3zKPI 7kj5fCkt5E9IYwot9chLXLlTFL4u2KkndIdkY9o=
X-Google-Smtp-Source: APXvYqxDwZJTrsrvdhUrVv2dvbSGJWf4/mlUTJeypRm6ACYPf6QlkKLzI+PnRolPalnvj7OkenC5J8BzOOJs6acGst0=
X-Received: by 2002:a0d:f6c2:: with SMTP id g185mr6610265ywf.167.1567081321689; Thu, 29 Aug 2019 05:22:01 -0700 (PDT)
MIME-Version: 1.0
References: <CANFmOtkrB=Z6HNyJ7SFinMAHJEgOB=J0KQnKxYqy_7kPYPbumg@mail.gmail.com> <20190829063910.GB90696@straasha.imrryr.org> <CANFmOt=_DqDNziVQh=5bF7yC-6DwPFPMYTz7kud7EwjsEFdY5Q@mail.gmail.com>
In-Reply-To: <CANFmOt=_DqDNziVQh=5bF7yC-6DwPFPMYTz7kud7EwjsEFdY5Q@mail.gmail.com>
From: Töma Gavrichenkov <ximaera@gmail.com>
Date: Thu, 29 Aug 2019 15:21:45 +0300
Message-ID: <CALZ3u+YbED9kc3MhEUf+AohoeC-WaHmFNJX_zBMNx84yZddMAQ@mail.gmail.com>
To: Naveen Kottapalli <naveen.sarma@gmail.com>
Cc: dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/zOXRNDnetTVPJ-2wmqt3BdOCNJU>
Subject: Re: [DNSOP] Why would a v4 client send AAAA query?
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, 29 Aug 2019 12:22:04 -0000

Peace,

On Thu, Aug 29, 2019 at 12:44 PM Naveen Kottapalli
<naveen.sarma@gmail.com> wrote:
> My query was about the behavior we observed on a gateway
> where a pure v4 subscriber (not dual-stack) has sent both A
> and AAAA query for the same domain simultaneously.  Just
> wanted to know why would a pure v4 subscriber which
> cannot use the resolved AAAA domain addresses is trying
> to resolve the v6 addresses of the domain.

In any way, that subscriber almost for sure has got v6 on the loopback
interface, and it is always possible that a domain name resolves to an
address within ::1.

--
Töma

v2.23.0 | Report a Bug | By Email