DiG - Internal error

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

DiG - Internal error

LeBlanc, Daniel James

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


_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/bind-users
Reply | Threaded
Open this post in threaded view
|

Re: DiG - Internal error

Tony Finch
LeBlanc, Daniel James <[hidden email]> wrote:
>
> 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:

dig +trace simulates iterative resolution so it tries to connect to
authoritative servers directly. This isn't going to work if you have
told it to bind the local end of the socket to 127.0.0.1.

> socket.c:4836: connect(192.112.36.4#53) 22/Invalid argument

For instance, observe that 192.112.36.4 is g.root-servers.net.

Tony.
--
f.anthony.n.finch  <[hidden email]>  http://dotat.at/
the fundamental values of liberty, equality, and community
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/bind-users
Reply | Threaded
Open this post in threaded view
|

RE: DiG - Internal error

LeBlanc, Daniel James
Thanks Tony - it is working now.  :-)

Daniel J. LeBlanc, P.Eng., MBA, DTME | Senior Network Architect | Bell Canada


-----Original Message-----
From: Tony Finch [mailto:[hidden email]]
Sent: June-11-19 11:03 AM
To: LeBlanc, Daniel James
Cc: ML BIND Users ([hidden email])
Subject: [EXT]Re: DiG - Internal error

LeBlanc, Daniel James <[hidden email]> wrote:
>
> 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:

dig +trace simulates iterative resolution so it tries to connect to
authoritative servers directly. This isn't going to work if you have
told it to bind the local end of the socket to 127.0.0.1.

> socket.c:4836: connect(192.112.36.4#53) 22/Invalid argument

For instance, observe that 192.112.36.4 is g.root-servers.net.

Tony.
--
f.anthony.n.finch  <[hidden email]>  http://dotat.at/
the fundamental values of liberty, equality, and community
------------------------------------------------------------------------------
External Email: Please use caution when opening links and attachments / Courriel externe: Soyez prudent avec les liens et documents joints

_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/bind-users