On Tue, 2009-12-29 at 07:39 -0800, Pamela Rock wrote: > > > [r...@test /]# dig aaaa ip6.test.com @bind6 +tcp > > +short socket.c:4922: 22/Invalid argument dig: > > isc_socket_connect: > > > unexpected error > [...] > This is a totally closed network. There is no access to anything.
I apologise because I am coming to this question very late and after not paying attention to the earlier messages in the thread. However: That looks a lot like what happens when a link local address is used with no scope qualifier. Here it is with plain old ping to one of my local machines: ka...@karl:~$ ping6 fe80::209:6bff:fe30:3e92 connect: Invalid argument But: ka...@karl:~$ ping6 fe80::209:6bff:fe30:3e92%wlan0 PING fe80::209:6bff:fe30:3e92%wlan0(fe80::209:6bff:fe30:3e92) 56 data bytes 64 bytes from fe80::209:6bff:fe30:3e92: icmp_seq=1 ttl=64 time=6.92 ms [...] So if your source address is a link local address, try adding a suitable scope qualifier. Again, my apologies if this has already been suggested and discarded. Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (ka...@biplane.com.au) +61-2-64957160 (h) http://www.biplane.com.au/~kauer/ +61-428-957160 (mob) GPG fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156 Old fingerprint: 07F3 1DF9 9D45 8BCD 7DD5 00CE 4A44 6A03 F43A 7DEF _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users