But doesn't that deal more with when you aren't running IPv6 on the
server? Or am i reading it wrong? I think we both have IPv6 enabled
and we are crashing.
On 2/24/2010 10:26 AM, Paul Wouters wrote:
On Wed, 24 Feb 2010, K Storbeck wrote:
I've had problems with version 1.4.1 on ipv6 too. After some (within an
hour) time, 2 of the 3 configured threads are eating up 100% cpu, and
the gathering of statistics through the command channel are failing
(i.e. I can connect to the port, but nothing happens).
You probably need svn commit r1953
- Fix for parent-child disagreement code which could have trouble
when (a) ipv6 was disabled and (b) the TTL for parent and child
were different. There were two bugs, the parent-side information
is fixed to no longer block lookup of child side information and
the iterator is fixed to no longer attempt to get ipv6 when it is
not enabled and then give up in failure.
Paul
_______________________________________________
Unbound-users mailing list
[email protected]
http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
--
Chris Gotstein
Sr Network Engineer
UP Logon/Computer Connection UP
500 N Stephenson Ave
Iron Mountain, MI 49801
Phone: 906-774-4847
Fax: 906-774-0335
[email protected]
_______________________________________________
Unbound-users mailing list
[email protected]
http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
