IETF Logo Mail Archive

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

Wes Hardaker <wjhns1@hardakers.net> Sat, 31 August 2019 15:30 UTC

Return-Path: <wjhns1@hardakers.net>
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 9EADF1200CD for <dnsop@ietfa.amsl.com>; Sat, 31 Aug 2019 08:30:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 OxoG7c611dqT for <dnsop@ietfa.amsl.com>; Sat, 31 Aug 2019 08:30:25 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C405120033 for <dnsop@ietf.org>; Sat, 31 Aug 2019 08:30:25 -0700 (PDT)
Received: from localhost (unknown [10.0.0.3]) by mail.hardakers.net (Postfix) with ESMTPA id 9AF0E2CBDD; Sat, 31 Aug 2019 08:30:24 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Naveen Kottapalli <naveen.sarma@gmail.com>
Cc: dnsop@ietf.org
References: <CANFmOtkrB=Z6HNyJ7SFinMAHJEgOB=J0KQnKxYqy_7kPYPbumg@mail.gmail.com>
Date: Sat, 31 Aug 2019 08:30:24 -0700
In-Reply-To: <CANFmOtkrB=Z6HNyJ7SFinMAHJEgOB=J0KQnKxYqy_7kPYPbumg@mail.gmail.com> (Naveen Kottapalli's message of "Wed, 28 Aug 2019 05:53:26 +0530")
Message-ID: <ybllfv9mjxr.fsf@w7.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lwAFhp6yZ5JK7dGISOvSdmGy0js>
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: Sat, 31 Aug 2019 15:30:27 -0000

Naveen Kottapalli <naveen.sarma@gmail.com> writes:

> Can one of you tell why would a v4 client send AAAA query or a by client send a
> A query when the resolved address cannot be used?

As others have pointed out it's very common.

As an example, I looked at all the requests arriving to a root server in
the DITL data for 2019-04-10 and found:

| IPv |                  |            |         |
|-----+------------------+------------+---------|
|   6 | count of all v6: |  328328681 |         |
|   6 | requesting A     |  169375042 | 0.51587 |
|   6 | requesting AAAA  |  121834127 | 0.37107 |
|   4 | count of all v4: | 2997023565 |         |
|   4 | count of A       | 1593723264 | 0.53177 |
|   4 | count of AAAA    |  326232540 | 0.10885 |

So you can see that of all the ipv4 clients, 53% were asking for A
records and 10.8% were asking for AAAA (the other requests were for
other types, eg DNSKEY/SOA/etc).  In the IPV6 space, it's even more
interesting that 51.6% of IPv6 clients were asking about A records, and
only 37% about AAAA!

-- 
Wes Hardaker
USC/ISI

v2.23.0 | Report a Bug | By Email