Bug 1455 - drill 1.7.0 - Error: error sending query: General LDNS error / Error: Could not find the nameserver ip addr; abort
drill 1.7.0 - Error: error sending query: General LDNS error / Error: Could n...
Status: NEW
Product: ldns
Classification: Unclassified
Component: drill/tools
unspecified
x86_64 Linux
: P5 normal
Assigned To: LDNS dev team
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-30 13:35 CEST by devurandom
Modified: 2017-09-30 13:35 CEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description devurandom 2017-09-30 13:35:43 CEST
drill fails without a useful error message when requesting a TCP connection:
$ drill -t google.com
Error: error sending query: General LDNS error

With -T it works for this domain (s.b.):
$ drill -tT google.com
.       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.
com.    172800  IN      NS      a.gtld-servers.net.
com.    172800  IN      NS      b.gtld-servers.net.
com.    172800  IN      NS      c.gtld-servers.net.
com.    172800  IN      NS      d.gtld-servers.net.
com.    172800  IN      NS      e.gtld-servers.net.
com.    172800  IN      NS      f.gtld-servers.net.
com.    172800  IN      NS      g.gtld-servers.net.
com.    172800  IN      NS      h.gtld-servers.net.
com.    172800  IN      NS      i.gtld-servers.net.
com.    172800  IN      NS      j.gtld-servers.net.
com.    172800  IN      NS      k.gtld-servers.net.
com.    172800  IN      NS      l.gtld-servers.net.
com.    172800  IN      NS      m.gtld-servers.net.
google.com.     172800  IN      NS      ns2.google.com.
google.com.     172800  IN      NS      ns1.google.com.
google.com.     172800  IN      NS      ns3.google.com.
google.com.     172800  IN      NS      ns4.google.com.
google.com.     300     IN      A       216.58.210.14

The problem seems to be present for all domains:
$ drill -t mailbox.org
Error: error sending query: General LDNS error

But in the case of mailbox.org, it appears to be even more weird, since drill claims it cannot find the nameserver's IP address:
$ drill -tT mailbox.org
.       518400  IN      NS      m.root-servers.net.
.       518400  IN      NS      j.root-servers.net.
.       518400  IN      NS      f.root-servers.net.
.       518400  IN      NS      d.root-servers.net.
.       518400  IN      NS      l.root-servers.net.
.       518400  IN      NS      g.root-servers.net.
.       518400  IN      NS      k.root-servers.net.
.       518400  IN      NS      h.root-servers.net.
.       518400  IN      NS      b.root-servers.net.
.       518400  IN      NS      e.root-servers.net.
.       518400  IN      NS      i.root-servers.net.
.       518400  IN      NS      a.root-servers.net.
.       518400  IN      NS      c.root-servers.net.
org.    172800  IN      NS      a0.org.afilias-nst.info.
org.    172800  IN      NS      b0.org.afilias-nst.org.
org.    172800  IN      NS      a2.org.afilias-nst.info.
org.    172800  IN      NS      d0.org.afilias-nst.org.
org.    172800  IN      NS      b2.org.afilias-nst.org.
org.    172800  IN      NS      c0.org.afilias-nst.info.
mailbox.org.    86400   IN      NS      ns3.jpberlin.de.
mailbox.org.    86400   IN      NS      ns.jpberlin.de.
mailbox.org.    86400   IN      NS      ns2.jpberlin.de.
Error: Could not find the nameserver ip addr; abort

Those nameservers (ns3.jpberlin.de., ns.jpberlin.de., ns2.jpberlin.de.) do have valid A records, when I query them:
$ drill a ns3.jpberlin.de. | grep -ve '^;' -e '^$'
ns3.jpberlin.de.        7160    IN      A       88.198.52.15

There seem to be no AAAA records, though I don't think that should pose a problem:
$ drill aaaa ns3.jpberlin.de.
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 25493
;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

The resolver set in /etc/resolv.conf is systemd-resolved 234.