From owner-freebsd-questions Wed Oct 8 00:14:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA27168 for questions-outgoing; Wed, 8 Oct 1997 00:14:41 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from neptune.ajc.state.net (neptune.ajc.state.net [204.120.158.168]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA27161 for ; Wed, 8 Oct 1997 00:14:37 -0700 (PDT) (envelope-from Al.Johnson@AJC.State.Net) Received: from AJC.State.Net (saturn.ajc.state.net [204.120.158.166]) by neptune.ajc.state.net (8.8.6/8.8.5) with ESMTP id CAA10600 for ; Wed, 8 Oct 1997 02:13:42 -0500 (CDT) Message-ID: <343B32D0.C2D8E9B9@AJC.State.Net> Date: Wed, 08 Oct 1997 02:14:24 -0500 From: Al Johnson Organization: Al Johnson Consulting X-Mailer: Mozilla 4.02 [en] (Win95; I) MIME-Version: 1.0 To: questions@FreeBSD.ORG Subject: Re: Good nameserver system? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Matthew D. Fuller wrote: > > On Wed, 8 Oct 1997, Greg Lehey wrote: > > > On Tue, Oct 07, 1997 at 10:36:22PM -0400, Kris Kirby wrote: > > > What would be a good system for making a nameserver? I'm guessing P-200 or > > > better and PPro-200. This would be a FreeBSD system, running named or a > > > faster nameserver. And a 500M-2GB disk cache. > > > > Are you planning to run a name server for a large network provider, > > including a large number of secondary servers? Then you might be on > > the right lines. I've always found that an old 386 with 8 MB of > > memory does a pretty good job. My name server, the primary for my > > domain, uses about 1 MB of data. In the last two days, it has used 22 > > seconds of CPU time on a P5/133. Depending on many things Named can grow to be a real best. I work on a DEC Alpha running the packaged Named (ya I know change to the latest release of BIND) and last night when I checked on it, it was consuming over 24MB of memory, virtually no disk space but way too much memory. -- Al