From owner-freebsd-stable Tue Apr 18 20:11:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 3608437B9D7 for ; Tue, 18 Apr 2000 20:11:36 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id TAA02518; Tue, 18 Apr 2000 19:23:46 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200004190223.TAA02518@freeway.dcfinc.com> Subject: Re: nat redirection In-Reply-To: <38FCE69F.23AEC923@owp.csus.edu> from Joseph Scott at "Apr 18, 0 03:50:07 pm" To: joseph.scott@owp.csus.edu (Joseph Scott) Date: Tue, 18 Apr 2000 19:23:46 -0700 (MST) Cc: matt@axl.net, freebsd-stable@FreeBSD.ORG Reply-To: chad@dcfinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The general feelings from people dealing with these issues seems to be > that split dns is also usually the easiest way to deal with this, even > though it does involve running another box and maintaining two sets of > dns records. We run a dual DNS at the office, one hands out addresses to the outside world, the other takes care of our internal systems. We've got a class B address block, so we're not NATing. But we do publish only a minor subset of all our systems to the outside. We do it on one box, though. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message