From owner-freebsd-questions Wed Feb 14 8:39:59 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.bnetmd.net (ns1.bnetmd.net [64.23.0.71]) by hub.freebsd.org (Postfix) with ESMTP id 32AA337B491 for ; Wed, 14 Feb 2001 08:39:55 -0800 (PST) Received: from localhost (freebsd@localhost) by mail.bnetmd.net (8.9.3/8.9.3) with ESMTP id LAA85456 for ; Wed, 14 Feb 2001 11:38:43 -0500 (EST) (envelope-from freebsd@mail.bnetmd.net) Date: Wed, 14 Feb 2001 11:38:43 -0500 (EST) From: Glenn McCalley To: freebsd-questions@freebsd.org Subject: named crashing 8.2.2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wathing the exchange on "named crashing"... and Uh Oh - come to think of it we had several named crashes within a couple of days a short while ago - nothing since - but just checked and we *are* running BIND 8.2.2. Checked CERT and sure enough there's that advisory. So! Upgrading BIND shouldn't be a big deal. But what's the chances we are harboring one of the Bad Guys - and if so whats the prodedure? Wipe, re-install and upgrade BIND? Is there something less than completely wiping the drives? Advice appreciated. Glenn. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message