DIG -6 +TCP
Pamela Rock
I've got closed lab testing BIND and I've got an interesting problem with IPv6 queries. Now I have 3 systems all running IPv4 and IPv6. IPv4 queries work fine across all systems. IPv6 UDP queries |
Pamela Rock
I've got a closed lab testing BIND and I've got an interesting problem with IPv6 queries. Now I have 3 systems all running IPv4 and IPv6. IPv4 queries work fine across all systems. IPv6 UDP queries work fine as well. When I test IPv6 TCP queries I get the following failure:
[root@dig-client ~]# dig -6 a test.domain @bindserver6 +tcp
socket.c:4922: 22/Invalid argument
dig: isc_socket_connect: unexpected error
Any ideas what would be causing this?
Thanks.
Doug Barton
Can you use other services over IPv6 in the lab? Also, what version of
BIND are you using? With 9.6.1-P1 I'm not having any problems with an
external query such as:
dig -6 @ns.isc.afilias-nst.info isc.org soa +tcp
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
Pamela Rock
> interesting problem with IPv6 queries. Now I have 3
> systems all running IPv4 and IPv6. IPv4 queries work
> fine across all systems. IPv6 UDP queries work fine as
> well. When I test IPv6 TCP queries I get the following
> failure:
> >
> >
> > [root@dig-client ~]# dig -6 a test.domain @bindserver6
> +tcp
> > socket.c:4922: 22/Invalid argument
> > dig: isc_socket_connect: unexpected error
>
> Can you use other services over IPv6 in the lab? Also, what
> version of
> BIND are you using? With 9.6.1-P1 I'm not having any
> problems with an
> external query such as:
>
> dig -6 @ns.isc.afilias-nst.info isc.org soa +tcp
>
I am using BIND 9.6.1-P1. Ping6 works, and I can run UDP based dig (+notcp) with no issues. IPv6 / TCP based queries fail.
Pamela Rock
> _______________________________________________
> bind-users mailing list
> bind-...@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
Doug Barton
> For all it's worth, using wireshark, I can see IPv6 UDP queries successfully traversing in/out. Ping6 works successfully. There is no firewall running anywhere(IPv4 or 6). Still get....
>
> [root@dig-client ~]# dig -6 a test.domain @bindserver6 +tcp
> socket.c:4922: 22/Invalid argument
> dig: isc_socket_connect: unexpected error
Ok, when you're using wireshark do you ever see TCP6 packets leaving
the box? Can you connect between machines using TCP6 for anything
else? And, what OS(es) are you using?
Cathy Almond
> Pamela Rock wrote:
>> For all it's worth, using wireshark, I can see IPv6 UDP queries successfully traversing in/out. Ping6 works successfully. There is no firewall running anywhere(IPv4 or 6). Still get....
>>
>> [root@dig-client ~]# dig -6 a test.domain @bindserver6 +tcp
>> socket.c:4922: 22/Invalid argument
>> dig: isc_socket_connect: unexpected error
>
> Ok, when you're using wireshark do you ever see TCP6 packets leaving
> the box? Can you connect between machines using TCP6 for anything
> else? And, what OS(es) are you using?
And, just in case you're not running what you expected...
dig -v
Danny Mayer
> Pamela Rock wrote:
>> For all it's worth, using wireshark, I can see IPv6 UDP queries successfully traversing in/out. Ping6 works successfully. There is no firewall running anywhere(IPv4 or 6). Still get....
>>
>> [root@dig-client ~]# dig -6 a test.domain @bindserver6 +tcp
>> socket.c:4922: 22/Invalid argument
>> dig: isc_socket_connect: unexpected error
>
> Ok, when you're using wireshark do you ever see TCP6 packets leaving
> the box? Can you connect between machines using TCP6 for anything
> else? And, what OS(es) are you using?
You won't get much from wireshark, dig is complaining about the
connect() function and there being something wrong with one of the
arguments. The 22 is the error code and the part after the slash is the
error message matching 22. It is possible that the socket being used is
of the wrong type for the address being connected to. If the socket
opened is an IPv6 socket and the obtained address for the nameserver
being queried happens to be an IPv4 address you could get this behavior.
Does bindserver6 have an A address as well as an AAAA address for the
nameserver?
Danny
Danny Mayer
> Doug Barton wrote:
>> Pamela Rock wrote:
>>> For all it's worth, using wireshark, I can see IPv6 UDP queries successfully traversing in/out. Ping6 works successfully. There is no firewall running anywhere(IPv4 or 6). Still get....
>>>
>>> [root@dig-client ~]# dig -6 a test.domain @bindserver6 +tcp
>>> socket.c:4922: 22/Invalid argument
>>> dig: isc_socket_connect: unexpected error
>> Ok, when you're using wireshark do you ever see TCP6 packets leaving
>> the box? Can you connect between machines using TCP6 for anything
>> else? And, what OS(es) are you using?
>
>
> dig -v
dig always prints its version when you run it unless you use +short!
Danny