From owner-freebsd-questions  Tue Oct  7 22:09:48 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA19485
          for questions-outgoing; Tue, 7 Oct 1997 22:09:48 -0700 (PDT)
          (envelope-from owner-freebsd-questions)
Received: from luke.cpl.net (luke.cpl.net [207.67.172.194])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA19479
          for <questions@FreeBSD.ORG>; Tue, 7 Oct 1997 22:09:45 -0700 (PDT)
          (envelope-from shawn@luke.cpl.net)
Received: from localhost (shawn@localhost) by luke.cpl.net (8.8.5/8.6.12) with SMTP id WAA01440; Tue, 7 Oct 1997 22:08:40 -0700 (PDT)
Date: Tue, 7 Oct 1997 22:08:39 -0700 (PDT)
From: Shawn Ramsey <shawn@luke.cpl.net>
To: Kris Kirby <kirbykb@airnet.net>
cc: questions@FreeBSD.ORG
Subject: Re: Good nameserver system?
In-Reply-To: <3431D65F0000D089@goliath.airnet.net> (added by goliath.airnet.net)
Message-ID: <Pine.BSF.3.95.971007220512.1317A-100000@luke.cpl.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 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.