From owner-freebsd-questions Tue Feb 13 17: 6: 1 2001 Delivered-To: freebsd-questions@freebsd.org Received: from gateway.cserisa.com (cserisa.com [64.241.217.100]) by hub.freebsd.org (Postfix) with ESMTP id 2F95F37B491 for ; Tue, 13 Feb 2001 17:05:58 -0800 (PST) Received: from server (www.aaweber.com [24.28.88.227]) by gateway.cserisa.com (8.9.3/8.9.3) with SMTP id TAA31830; Tue, 13 Feb 2001 19:05:52 -0600 (CST) (envelope-from aaweber@cserisa.com) Reply-To: From: "Alan Weber" To: "'Matthew Emmerton'" Cc: Subject: RE: Question: bind / named problem Date: Tue, 13 Feb 2001 19:04:44 -0600 Message-ID: <01c501c09622$466e6bb0$e400000a@aawhome.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-reply-to: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Upgrade bind to 8.2.3-rel. The latest bind security advisories mention that named can be crashed with potential exploits that will allow root access. I am not sure if there is a root exposure in FreeBSD, but it is annoying to have to restart DNS whenever some kiddie knocks on the door. There may be a script kiddie package as I have been hit on servers in 5 states on three different network providers. I cvsupd to 3.5-stable and went thru buildworld/installworld just to be safe. -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Matthew Emmerton Sent: Tuesday, February 13, 2001 1:20 AM To: Ted Mittelstaedt Cc: Scott Hyjek; 'freebsd-questions@FreeBSD.ORG' Subject: Re: Question: bind / named problem On Mon, 12 Feb 2001, Ted Mittelstaedt wrote: > Quoting Scott Hyjek : > > > Any information or guidance would be appreciated. We've experienced a > > problem on our external DNS twice now (last thursday and Sunday). Name > > resolution ceases and we receive the following: > > quentin/kernel: pid 104 (named), uid 0: exited on signal 6 (core dumped) > > > > make sure your free space is not running low I've been having similar problems on a 3.4-R box (it will be upgraded to 4.x as soon as the ata driver works with my 500MB Quantum HDD) How much "free space" is enough? -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message