On 11/26/14 12:48 PM, Niall O'Reilly 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'd expect that to be enough, unless there's a typo in the address.
It's not a typo.
I have for some reason
listen-on-v6 { all; };
It might be worth checking whether this makes a difference.
+1 to this.
Also, I am wondering what version of named you're running, Jared. I've
got 9.9.6 with the same type of listen-on* as you, and it works.
I'm using your free secondary on puck, so I'm happy to return the favor
with more assistance if needed. :)
Doug
_______________________________________________
dns-operations mailing list
[email protected]
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
dns-jobs mailing list
https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
