Date: Thu, 8 Feb 2007 15:51:48 -0500 From: Javier Henderson <javier@kjsl.com> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, Steven Bens <steven@unix-solutions.be> Subject: Re: Serious Bind issue Message-ID: <DFB7F010-D084-45EB-AE11-B6083424EEC6@kjsl.com> In-Reply-To: <45CB8C33.7020608@FreeBSD.org> References: <20070208092346.072F513C47E@mx1.freebsd.org> <45CB8C33.7020608@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 8, 2007, at 3:46 PM, Doug Barton wrote: > In the future, please don't cross post to both freebsd-questions, and > another list at the same time. Thanks. > > Steven Bens wrote: >> Dear mailinglist members, >> >> I have an serious issue with bind. >> >> System information: >> Dual P3 1 GHz >> 6.1-RELEASE-p12 FreeBSD >> SMP kernel >> >> I'm running BIND 9.3.2 on this box (the one that is standard >> delivered with >> 6.1) >> And when the named is running for a copple of hours. Bind doesn't >> accept TCP >> connections > > In an ideal world you would upgrade to the latest RELENG_6 and pick up > all the bug fixes in the OS, plus the latest version of BIND. If > that's not possible for some reason, your best bet is to upgrade to > the latest BIND from the ports, make sure that you build it WITHOUT > threads, and see if that resolves the issue for you. FWIW, I was running BIND 9.3.2 for a while and in awe at the amount of memory it would use, and how it would go CPU bound after it hit any operating system imposed memory quotas. I went back to BIND 8.latest, and my problems went away. -jav
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DFB7F010-D084-45EB-AE11-B6083424EEC6>