Whoops. I had meant to add this to bug#205926 (bind9 named stops receiving on some interfaces). My setup works equally poorly if IPv6 is disabled...
------Original Message------ From: Pascal Hambourg To: Brian Ristuccia Sent: Jan 22, 2008 4:39 AM Subject: Re: Bug#310772: bind9: unexpected error @ client.c:1325 stops IPv6responses Hello, Brian Ristuccia wrote : > Also broken in the 1:9.3.4-2etch1 version in etch. > > In my configuration, I see the problem on several interfaces relatively > quickly after named starts running. This bug makes named mostly unusable. I haven't upgraded my system to etch yet, so thanks for the feedback. Depending on your system setup, networking environment and operational requirements, there may be some possible workarounds mitigating the bug. On my system, bind9 works fine with with the kernel parameter bindv6only set to 1. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
