Report information
The Basics
Id:
40420
Status:
resolved
Priority:
Medium/Medium
Queue:

People
Owner:
Nobody in particular
Cc:
AdminCc:

BugTracker
Version Fixed:
9.11.0
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
9.11
Priority:
(no value)
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
feature

Dates
Created:Thu, 20 Aug 2015 11:15:10 -0400
Updated:Fri, 07 Jul 2017 19:44:00 -0400
Closed:Thu, 21 Jul 2016 16:35:21 -0400



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

CC: "Tomas Hozza" <thozza@redhat.com>
Subject: [PATCH] Make nslookup lookup both A and AAAA records by default
Date: Thu, 20 Aug 2015 11:15:05 -0400 (EDT)
To: bind-suggest@isc.org
From: "Jakub Luzny" <jluzny@redhat.com>
Hello, I'm sending a patch that changes the default behavior of nslookup. Currently, nslookup fetches only A records by default. As the IPv6 transition moves ahead, I think it's unreasonable to expect the user to manually specify that he wants an AAAA query. Changes: 1) Modified nslookup's default behavior to host-like behavior. After receiving reply to A query, it sends an AAAA query. This is only default behavior, it's disabled when user specifies type on command line or in interactive mode. 2) Modified the format of printing an AAAA response to be the same like for a A response. Original: > star.c10r.facebook.com has AAAA address 2a03:2880:f01c:2:face:b00c:0:1 Patched: > Name: star.c10r.facebook.com > Address: 2a03:2880:f01c:2:face:b00c:0:1 3) Disabled "Authoritative answers can be found from:" output for AAAA query, as it was already disabled for A query and I don't see any reason for different behavior Example outputs: 1) Original: $ nslookup www.facebook.com Server: 10.38.5.26 Address: 10.38.5.26#53 Non-authoritative answer: www.facebook.com canonical name = star.c10r.facebook.com. Name: star.c10r.facebook.com Address: 31.13.93.3 Patched: $ ./nslookup www.facebook.com Server: 10.38.5.26 Address: 10.38.5.26#53 Non-authoritative answer: www.facebook.com canonical name = star.c10r.facebook.com. Name: star.c10r.facebook.com Address: 31.13.93.3 Name: star.c10r.facebook.com Address: 2a03:2880:f01c:2:face:b00c:0:1 2) Original: $ nslookup v6.vvv.facebook.com Server: 10.38.5.26 Address: 10.38.5.26#53 Non-authoritative answer: *** Can't find v6.vvv.facebook.com: No answer Patched: $ ./nslookup v6.vvv.facebook.com Server: 10.38.5.26 Address: 10.38.5.26#53 Non-authoritative answer: Name: v6.vvv.facebook.com Address: 2a03:2880:20:8f08:face:b00c:0:1 3) Original: $ nslookup -type=aaaa www.facebook.com Server: 10.38.5.26 Address: 10.38.5.26#53 Non-authoritative answer: www.facebook.com canonical name = star.c10r.facebook.com. star.c10r.facebook.com has AAAA address 2a03:2880:f01c:2:face:b00c:0:1 Authoritative answers can be found from: Patched: $ ./nslookup -type=aaaa www.facebook.com Server: 10.38.5.26 Address: 10.38.5.26#53 Non-authoritative answer: www.facebook.com canonical name = star.c10r.facebook.com. Name: star.c10r.facebook.com Address: 2a03:2880:f01c:2:face:b00c:0:1 Jakub Luzny

Message body is not shown because sender requested not to inline it.

Subject: Re: [ISC-Bugs #40420] AutoReply: [PATCH] Make nslookup lookup both A and AAAA records by default
Date: Thu, 3 Sep 2015 03:31:34 -0400 (EDT)
To: bind-suggest@isc.org
From: "Jakub Luzny" <jluzny@redhat.com>
Hello, I just want to ask if there is something wrong with this patch? Feel free to complain to me. Thanks, Jakub Luzny
CC:
Subject: Re: [ISC-Bugs #40420] AutoReply: [PATCH] Make nslookup lookup both A and AAAA records by default
Date: Thu, 3 Sep 2015 17:35:13 +0000
To: "Jakub Luzny via RT" <bind-suggest@isc.org>
From: "Evan Hunt" <each@isc.org>
On Thu, Sep 03, 2015 at 07:31:40AM +0000, Jakub Luzny via RT wrote: > I just want to ask if there is something wrong with this patch? Not so far as I know, but we've been quite busy with security releases over the past couple of weeks. We'll get to it shortly. Thank you for the reminder.