[dns-operations] Bind v6 TCP listen?

[Jared Mauch]

> On Nov 26, 2014, at 3:48 PM, Niall O'Reilly <niall.oreilly at ucd.ie> wrote:
> 
> At Wed, 26 Nov 2014 12:37:57 -0500,
> Jared Mauch wrote:
>> 
>> Is there some specific configuration magic that I’m missing to make
>> bind listen to TCPv6 sockets?
> 
>  [...]
> 
>> My configuration is fairly straightforward, including manual
>> listen-on segments, e.g.:
>> 
>>        listen-on { 204.42.254.5; };
>>        listen-on-v6 { 2001:418:3f4::5; };
> 
>  I realize I'm at risk of "teaching my grandmother to suck eggs", but
>  reckon you must be dealing with something which is either really
>  obscure or hidden in plain sight, so here goes ...
> 
>  I'ld expect that to be enough, unless there's a typo in the address.
> 
>  I have for some reason
> 
> 	listen-on-v6 { all; };
> 
>  It might be worth checking whether this makes a difference.


Thanks everyone.  Looks like this is actually a bug in bind, or the one packaged with FC21 (at least).

With any it seems to do the right thing:

named   909 named   20u     IPv4              24571      0t0      TCP 204.42.254.5:domain (LISTEN)
named   909 named   21u     IPv4              28306      0t0      TCP 127.0.0.1:rndc (LISTEN)
named   909 named   22u     IPv4           18812144      0t0      TCP 204.42.254.5:domain->217.21.61.8:21683 (ESTABLISHED)
named   909 named   23u     IPv6           18810485      0t0      TCP *:domain (LISTEN)
named   909 named  512u     IPv4              24570      0t0      UDP 204.42.254.5:domain 
named   909 named  513u     IPv4              24570      0t0      UDP 204.42.254.5:domain 
named   909 named  514u     IPv4           18809462      0t0      UDP *:13642 
named   909 named  516u     IPv6           18810484      0t0      UDP *:domain 
named   909 named  518u     IPv6           18810484      0t0      UDP *:domain 

I’ll have to do some more testing later, back to family time.

- Jared