FS#74010 - [bind] nslookup with option always prints debug output

Attached to Project: Arch Linux
Opened by Rajiv Aaron Manglani (rajiv) - Wednesday, 02 March 2022, 14:13 GMT
Last edited by David Thurstenson (thurstylark) - Wednesday, 23 March 2022, 18:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After upgrade package bind from 9.16.25-1 to 9.18.0-1, the command `nslookup` always prints debug output when used with keyword options.


Steps to reproduce:
Call `nslookup` with a `-type` or other keyword option. `nslookup` should not print debug output in these cases.

Incorrect output:

```
$ nslookup -version
nslookup 9.18.0

$ nslookup archlinux.org
Server: 97.107.133.4
Address: 97.107.133.4#53

Non-authoritative answer:
Name: archlinux.org
Address: 95.217.163.246
Name: archlinux.org
Address: 2a01:4f9:c010:6b1f::1

$ nslookup -type=ns archlinux.org
main parsing archlinux.org
addlookup()
make_empty_lookup()
make_empty_lookup() = 0x7f9e3ff9e000->references = 1
looking up archlinux.org
lock_lookup dighost.c:4184
success
start_lookup()
setup_lookup(0x7f9e3ff9e000)
resetting lookup counter.
cloning server list
clone_server_list()
... lots more debug output
```


Correct output from a non-archlinux system:
```
$ nslookup -version
nslookup 9.11.5-P4-5.1+deb10u6-Raspbian

$ nslookup -type=ns archlinux.org
Server: 100.100.100.100
Address: 100.100.100.100#53

Non-authoritative answer:
archlinux.org nameserver = hydrogen.ns.hetzner.com.
archlinux.org nameserver = oxygen.ns.hetzner.com.
archlinux.org nameserver = helium.ns.hetzner.de.

Authoritative answers can be found from:

```


This task depends upon

Closed by  David Thurstenson (thurstylark)
Wednesday, 23 March 2022, 18:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  bind 9.18.1-1
Comment by loqs (loqs) - Wednesday, 02 March 2022, 14:34 GMT Comment by Rajiv Aaron Manglani (rajiv) - Friday, 18 March 2022, 13:07 GMT
This issue has been fixed in bind 9.18.1-1. Thanks.

Loading...