From owner-freebsd-questions Wed Oct 8 05:18:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA14029 for questions-outgoing; Wed, 8 Oct 1997 05:18:25 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from houseofduck.ml.org (geo-160.remote.dti.net [206.252.145.160]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA14021 for ; Wed, 8 Oct 1997 05:18:21 -0700 (PDT) (envelope-from shaggy@houseofduck.ml.org) Received: from houseofduck.ml.org (localhost.ml.org [127.0.0.1]) by houseofduck.ml.org (8.8.7/8.8.7) with ESMTP id IAA00258; Tue, 7 Oct 1997 08:20:04 -0400 (EDT) Message-ID: <343A28F3.ECFD5F1A@houseofduck.ml.org> Date: Tue, 07 Oct 1997 08:20:03 -0400 From: Joshua Fielden Reply-To: jfielden@geocities.com Organization: GeoCities X-Mailer: Mozilla 4.02b7 [en] (X11; I; FreeBSD 2.2-970903-RELENG i386) MIME-Version: 1.0 To: Shawn Ramsey CC: Kris Kirby , 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 Shawn Ramsey 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. > > A P133 with 64MB on RAM should be able to handle just about any namesever > you could throw at it. Nameserving is not at all CPU intensive. Currently, the New York office here at GeoCities is using a P120 laptop with 16 megs of RAM for DNS/ftp/www, and working just fine. :-) -- This is a test of the Emergency Broadcast System. If this had been an actual life-threatening emergency, we would have fled in terror, and you would not have been informed. -- Joshua Fielden, Systems Administrator, GeoCities http://www.geocities.com jfielden@geocities.com I do not speak for my company, all opinions enclosed in this e-mail are purely my own.