From owner-freebsd-isp Tue Feb 27 14:17:56 2001 Delivered-To: freebsd-isp@freebsd.org Received: from bogon.kjsl.com (bogon.kjsl.com [206.55.236.195]) by hub.freebsd.org (Postfix) with ESMTP id 0552237B718 for ; Tue, 27 Feb 2001 14:17:52 -0800 (PST) (envelope-from javier@bogon.kjsl.com) Received: (from javier@localhost) by bogon.kjsl.com (8.11.1/8.11.1) id f1RMJAj95689; Tue, 27 Feb 2001 14:19:10 -0800 (PST) From: Javier Henderson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15004.10206.479329.263452@bogon.kjsl.com> Date: Tue, 27 Feb 2001 14:19:10 -0800 (PST) To: "Troy Settle" Cc: "Leif Neland" , Subject: RE: tinydns In-Reply-To: References: X-Mailer: VM 6.71 under Emacs 19.34.1 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Troy Settle writes: > I don't know, perhaps it's the fact that it's the only daemon that's dumping > core (sig 11) on a fairly unloaded server. When I posted earlier today, > it's done it twice in a week, it dumped again this afternoon. I'm running > 8.2.3, and that's teh current "stable" version listed on ISC's web site. I'm not seeing that at all here (4.2-STABLE, 8.2.3 as of last week, and authoritative for close to 400 domains). > I appreciate that BIND is used by hundreds of thousands (if not millions) of > networks around the world, but it's been less than reliable here. I've been > using various versions of BIND for some 6 years now, and I've never seen it > behave like this. In addition to that, if one is to believe the security > warnings, everything before 8.2.3 has holes in it, and just because one's > not been found, doesn't mean that 8.2.3 doesn't have one either. You can say that about any piece of code, though. -jav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message