drill -T -x

Using the drill command with the -T option seems to work well enough
when the argument is some ordinary sort of FQDN.

Is it just me or do other people also experience some less than adequate
output when and if the drill command is used -both- with the -T option
-and- also with the -x option?

Example:

   drill -T -x 195.154.23.103

Ronald F. Guilmette via Unbound-users:

   drill -T -x 195.154.23.103

yes, same here: ( ldns-1.7.0 )

$ drill -T debian.org
. 518400 IN NS a.root-servers.net.
. 518400 IN NS b.root-servers.net.
. 518400 IN NS c.root-servers.net.
. 518400 IN NS d.root-servers.net.
. 518400 IN NS e.root-servers.net.
. 518400 IN NS f.root-servers.net.
. 518400 IN NS g.root-servers.net.
. 518400 IN NS h.root-servers.net.
. 518400 IN NS i.root-servers.net.
. 518400 IN NS j.root-servers.net.
. 518400 IN NS k.root-servers.net.
. 518400 IN NS l.root-servers.net.
. 518400 IN NS m.root-servers.net.
org. 172800 IN NS a0.org.afilias-nst.info.
org. 172800 IN NS a2.org.afilias-nst.info.
org. 172800 IN NS b0.org.afilias-nst.org.
org. 172800 IN NS b2.org.afilias-nst.org.
org. 172800 IN NS c0.org.afilias-nst.info.
org. 172800 IN NS d0.org.afilias-nst.org.
debian.org. 86400 IN NS sec2.rcode0.net.
debian.org. 86400 IN NS dns4.easydns.info.
debian.org. 86400 IN NS sec1.rcode0.net.
debian.org. 86400 IN NS nsp.dnsnode.net.
debian.org. 300 IN A 128.31.0.62
debian.org. 300 IN A 5.153.231.4
debian.org. 300 IN A 149.20.4.15
debian.org. 300 IN A 130.89.148.14

but:
$ drill -T -x 130.89.148.14
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 45490
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; 14.148.89.130.in-addr.arpa. IN PTR

;; ANSWER SECTION:
14.148.89.130.in-addr.arpa. 86400 IN PTR klecker-misc.debian.org.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 343 msec
;; SERVER: 127.0.0.1
;; WHEN: Fri Jun 21 09:53:31 2019
;; MSG SIZE rcvd: 81

In message <20190621095353.Horde.4xtvD53MUKwjpxAK46ryokt@andreasschulze.de>,

Ronald F. Guilmette via Unbound-users:

   drill -T -x 195.154.23.103

yes, same here: ( ldns-1.7.0 )

OK, so someone else just informed me that he had looked at the source
code for drill and that it just plain doesn't support the use of both
-T and -x together.

So I have two confirmations now. I am ready to file a formal bug report
on this. But there's a catch...

I am looking at the relevant bugzilla home page and I don't see anyplace
where I can create an account. Am I just missing it? (I *do* need new
glasses, but I didn't think my eyesight was really THAT bad yet.)

    https://www.nlnetlabs.nl/bugs-script/

Regards,
rfg

P.S. The following is relevant only to people who elect to use the
BIND "dig" command in preference to the unbound "drill" command.

This is just FYI --

I have been informed that there is a small and subtle issue with
the BIND 9.x.x versions of the "dig +trace" command, prior to
9.14.3 that cause it not to work when used in conjunction with
either unbound or local-unbound:

    https://lists.isc.org/pipermail/bind-users/2019-June/101954.html

Hi Ronald,

I am looking at the relevant bugzilla home page and I don't see anyplace
where I can create an account. Am I just missing it? (I *do* need new
glasses, but I didn't think my eyesight was really THAT bad yet.)

    https://www.nlnetlabs.nl/bugs-script/

All the NlNetLabs projects have moved to GitHub. Please open your bug
report here:

https://github.com/NLnetLabs/ldns

Regards,
Anand

In message <1322dac8-70ce-0f7b-3c11-9c4589aa4ba3@ripe.net>,