From owner-freebsd-net@FreeBSD.ORG Thu Feb 8 21:18:28 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3222116A402; Thu, 8 Feb 2007 21:18:28 +0000 (UTC) (envelope-from javier@kjsl.com) Received: from skywagon.kjsl.com (skywagon.kjsl.com [69.36.240.252]) by mx1.freebsd.org (Postfix) with ESMTP id 1F24A13C4A3; Thu, 8 Feb 2007 21:18:28 +0000 (UTC) (envelope-from javier@kjsl.com) Received: from [199.46.16.11] (rtp-isp-nat1.cisco.com [64.102.254.33]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: javier) by skywagon.kjsl.com (Postfix) with ESMTP id 1E4E42A68CC; Thu, 8 Feb 2007 15:51:52 -0500 (EST) In-Reply-To: <45CB8C33.7020608@FreeBSD.org> References: <20070208092346.072F513C47E@mx1.freebsd.org> <45CB8C33.7020608@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Javier Henderson Date: Thu, 8 Feb 2007 15:51:48 -0500 To: Doug Barton X-Mailer: Apple Mail (2.752.2) Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, Steven Bens Subject: Re: Serious Bind issue X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Feb 2007 21:18:28 -0000 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