[92395] in North American Network Operators' Group
Re: Why is RFC1918 space in public DNS evil?
daemon@ATHENA.MIT.EDU (Elijah Savage)
Mon Sep 18 15:55:24 2006
Date: Mon, 18 Sep 2006 15:54:31 -0400 (EDT)
From: Elijah Savage <esavage@digitalrage.org>
To: Roland Dobbins <rdobbins@cisco.com>
Cc: nanog@merit.edu
In-Reply-To: <7B40411F-CF73-496E-AEB4-123007CA24D6@cisco.com>
Errors-To: owner-nanog@merit.edu
----- Original Message -----
From: Roland Dobbins <rdobbins@cisco.com>
To: nanog@merit.edu
Sent: Monday, September 18, 2006 3:17:01 PM GMT-0500
Subject: Re: Why is RFC1918 space in public DNS evil?
On Sep 18, 2006, at 12:12 PM, Elijah Savage wrote:
> I've been directed to put all of the internal hosts and such into
> the public
> DNS zone for a client.
>Another option is split-horizon DNS for the internal stuff, if it
>never needs to be publicly visible.
Yes, that's what views will give you. You have an internal view only your vpn and lan users can see. Then you have a public view for all others that do not mix. All can be run on the same servers vice having 2 external and 2 internal name servers and also without having to run multiple instances of bind.
