DiG - Internal error
LeBlanc, Daniel James
daniel.leblanc at bellaliant.ca
Tue Jun 11 13:54:16 UTC 2019
Hello.
I am using the dig that was created during the compile of BIND 9.14.0 (Stable Release) <id:90df20a>.
I am performing a dig command from and against localhost and that has firewalled access to the Internet but am getting an exit status of 10 and the following textual error:
Ø /var/named/bin/dig @<server IP> -b127.0.0.1 google.ca. ANY +trace
; <<>> DiG 9.14.0 <<>> @<server IP> -b127.0.0.1 google.ca. ANY +trace
; (1 server found)
;; global options: +cmd
. 355709 IN NS k.root-servers.net.
. 355709 IN NS i.root-servers.net.
. 355709 IN NS j.root-servers.net.
. 355709 IN NS m.root-servers.net.
. 355709 IN NS l.root-servers.net.
. 355709 IN NS b.root-servers.net.
. 355709 IN NS g.root-servers.net.
. 355709 IN NS f.root-servers.net.
. 355709 IN NS d.root-servers.net.
. 355709 IN NS h.root-servers.net.
. 355709 IN NS e.root-servers.net.
. 355709 IN NS c.root-servers.net.
. 355709 IN NS a.root-servers.net.
. 355709 IN RRSIG NS 8 0 518400 20190622050000 20190609040000 25266 . G8w4S+a5KX6xmpBny4ATqGATyH7aN7704Yq0k3rugC1z19e/ccgLBLbv nTNmWdHTNgFlp+5DaDtQfOK2jBH/FT/EFCRMcu0fsWxcJGW8nzvDptTs Gcdc3T23OGKjdHsOMnQq98bgpuW4giKDNp5Sun5HsN5CiqzHORgdaKCu bsfvD9EDeX1PdEMppzWiSl2TvYPGoaYIGnVvsprfgigofCoTtKEpD52Z RjcMEDIPwBdWQ8XL4DRdUeZ0XTNi76ParfRMErZkfV/Yp9PIG1J45ppv aZqXQUoyew8n4Zuq4G5LDr//exOGoTbsxrxFJcbtyHrAVJ0uhZeJdxKf sg0KHw==
;; Received 565 bytes from <server IP>#53(<server IP>) in 2 ms
socket.c:4836: connect(192.112.36.4#53) 22/Invalid argument
/var/named/bin/dig: isc_socket_connect: unexpected error
I tried with the version of dig that was provided with RHEL 7.5 and obtained an error with it as well (although it is a bit different and in this case the exit status was 0):
Ø dig @<server IP> -b127.0.0.1 google.ca. ANY +trace
; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7_5.1 <<>> @<server IP> -b127.0.0.1 google.ca. ANY +trace
; (1 server found)
;; global options: +cmd
. 355278 IN NS j.root-servers.net.
. 355278 IN NS a.root-servers.net.
. 355278 IN NS m.root-servers.net.
. 355278 IN NS b.root-servers.net.
. 355278 IN NS g.root-servers.net.
. 355278 IN NS d.root-servers.net.
. 355278 IN NS k.root-servers.net.
. 355278 IN NS f.root-servers.net.
. 355278 IN NS h.root-servers.net.
. 355278 IN NS i.root-servers.net.
. 355278 IN NS c.root-servers.net.
. 355278 IN NS l.root-servers.net.
. 355278 IN NS e.root-servers.net.
. 355278 IN RRSIG NS 8 0 518400 20190622050000 20190609040000 25266 . G8w4S+a5KX6xmpBny4ATqGATyH7aN7704Yq0k3rugC1z19e/ccgLBLbv nTNmWdHTNgFlp+5DaDtQfOK2jBH/FT/EFCRMcu0fsWxcJGW8nzvDptTs Gcdc3T23OGKjdHsOMnQq98bgpuW4giKDNp5Sun5HsN5CiqzHORgdaKCu bsfvD9EDeX1PdEMppzWiSl2TvYPGoaYIGnVvsprfgigofCoTtKEpD52Z RjcMEDIPwBdWQ8XL4DRdUeZ0XTNi76ParfRMErZkfV/Yp9PIG1J45ppv aZqXQUoyew8n4Zuq4G5LDr//exOGoTbsxrxFJcbtyHrAVJ0uhZeJdxKf sg0KHw==
;; Received 537 bytes from <server IP>#53(<server IP>) in 14 ms
socket.c:1949: internal_send: 192.58.128.30#53: Invalid argument
socket.c:1949: internal_send: 193.0.14.129#53: Invalid argument
socket.c:1949: internal_send: 192.5.5.241#53: Invalid argument
socket.c:1949: internal_send: 192.36.148.17#53: Invalid argument
socket.c:1949: internal_send: 192.33.4.12#53: Invalid argument
socket.c:1949: internal_send: 199.9.14.201#53: Invalid argument
socket.c:1949: internal_send: 192.112.36.4#53: Invalid argument
socket.c:1949: internal_send: 199.7.83.42#53: Invalid argument
socket.c:1949: internal_send: 199.7.91.13#53: Invalid argument
socket.c:1949: internal_send: 192.203.230.10#53: Invalid argument
socket.c:1949: internal_send: 198.97.190.53#53: Invalid argument
socket.c:1949: internal_send: 198.41.0.4#53: Invalid argument
socket.c:1949: internal_send: 202.12.27.33#53: Invalid argument
socket.c:1949: internal_send: 192.58.128.30#53: Invalid argument
socket.c:1949: internal_send: 193.0.14.129#53: Invalid argument
socket.c:1949: internal_send: 192.5.5.241#53: Invalid argument
socket.c:1949: internal_send: 192.36.148.17#53: Invalid argument
socket.c:1949: internal_send: 192.33.4.12#53: Invalid argument
socket.c:1949: internal_send: 199.9.14.201#53: Invalid argument
socket.c:1949: internal_send: 192.112.36.4#53: Invalid argument
socket.c:1949: internal_send: 199.7.83.42#53: Invalid argument
socket.c:1949: internal_send: 199.7.91.13#53: Invalid argument
socket.c:1949: internal_send: 192.203.230.10#53: Invalid argument
socket.c:1949: internal_send: 198.97.190.53#53: Invalid argument
socket.c:1949: internal_send: 198.41.0.4#53: Invalid argument
socket.c:1949: internal_send: 202.12.27.33#53: Invalid argument
socket.c:1949: internal_send: 192.58.128.30#53: Invalid argument
socket.c:1949: internal_send: 193.0.14.129#53: Invalid argument
socket.c:1949: internal_send: 192.5.5.241#53: Invalid argument
socket.c:1949: internal_send: 192.36.148.17#53: Invalid argument
socket.c:1949: internal_send: 192.33.4.12#53: Invalid argument
socket.c:1949: internal_send: 199.9.14.201#53: Invalid argument
Is this a bug, is something on my server configured incorrectly or am I performing my query incorrectly?
Thanks!
Daniel J. LeBlanc, P.Eng., MBA, DTME | Senior Network Architect | Bell Canada
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20190611/b5421c01/attachment-0001.html>
More information about the bind-users
mailing list