IPv6 TCP

[Pamela Rock]

--- On Mon, 12/28/09, Kevin Oberman <oberman at es.net> wrote:

> From: Kevin Oberman <oberman at es.net>
> Subject: Re: IPv6 TCP
> To: "Pamela Rock" <prock111 at yahoo.com>
> Cc: "Mark Andrews" <marka at isc.org>, "Chuck Anderson" <cra at WPI.EDU>, bind-users at lists.isc.org
> Date: Monday, December 28, 2009, 10:08 PM
> > Date: Mon, 28 Dec 2009 18:02:29
> -0800 (PST)
> > From: Pamela Rock <prock111 at yahoo.com>
> > 
> > 
> > 
> > --- On Mon, 12/28/09, Mark Andrews <marka at isc.org>
> wrote:
> > 
> > > From: Mark Andrews <marka at isc.org>
> > > Subject: Re: IPv6 TCP
> > > To: "Pamela Rock" <prock111 at yahoo.com>
> > > Cc: "Kevin Oberman" <oberman at es.net>,
> "Chuck Anderson" <cra at WPI.EDU>, bind-users at lists.isc.org
> > > Date: Monday, December 28, 2009, 8:22 PM
> > > 
> > > In message <475084.65186.qm at web110304.mail.gq1.yahoo.com>,
> > > Pamela Rock writes:
> > > > This query is to anyone in general, based on
> the
> > > previous dig statement, do=
> > > > es the following command make sense??
> > > > 
> > > > dig -6 www.es.net @some:ipv6:address +tcp
> > > > 
> > > > I'm wondering if the combination of -6,
> > > @some:ipv6:address, and +tcp even m=
> > > > ake sense.  That is ultimately what I'm
> trying to
> > > achieve.
> > > 
> > > Yes, it make sense.  The following will retrieve
> the
> > > SOA record
> > > from ns-ext.isc.org using its IPv6 address over
> tcp. 
> > > If you put a
> > > literal IPv6 address rather than a name then the
> -6 is not
> > > needed.
> > 
> > That's it!!  So you are saying if I can use
> either -6 or
> > MY:IPv6:Address, but I don't have to use both? 
> Is that accurate?  If
> > so, that resolves the issue.
> 
> If you tell dig(1) to query an IPv6 address, it has no
> choice but to
> use IPv6, so -6 is unnecessary and -4 is an error. The only
> reason
> for the -4 and -6 options is to force that protocol to be
> used when a
> name is provided and it has both v4 and v6 addresses.
> 
> That said, using -6 with an IPv6 address should not cause a
> problem. It
> certainly works fine for me.

Yeah, you're right, it still does not work even with the -6 left off.  I thought that would provide the correct response...

This works...
[root at test /]# dig aaaa ip6.test.com @bind6 +notcp +short
e:1900:4545:3:200:f8ff:fe21:67cf

This does not...
[root at test /]# dig aaaa ip6.test.com @bind6 +tcp +short
socket.c:4922: 22/Invalid argument
dig: isc_socket_connect: unexpected error

That last query never leaves the client resolver so the DNS does not see it.  Using wireshark, there is no traffic between client and server.

I'm stumped.

> -- 
> R. Kevin Oberman, Network Engineer
> Energy Sciences Network (ESnet)
> Ernest O. Lawrence Berkeley National Laboratory (Berkeley
> Lab)
> E-mail: oberman at es.net   
>         Phone: +1 510
> 486-8634
> Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D
> EBB3 987B 3751
>