From owner-freebsd-questions@FreeBSD.ORG Mon Jul 2 22:46:00 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D90CC16A46B for ; Mon, 2 Jul 2007 22:46:00 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from conn-smtp.mc.mpls.visi.com (conn.mc.mpls.visi.com [208.42.156.2]) by mx1.freebsd.org (Postfix) with ESMTP id B00CA13C447 for ; Mon, 2 Jul 2007 22:46:00 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from mail.tcbug.org (mail.tcbug.org [208.42.70.163]) by conn-smtp.mc.mpls.visi.com (Postfix) with ESMTP id E467581D5; Mon, 2 Jul 2007 17:19:55 -0500 (CDT) Received: from roadrash.local (unknown [192.168.2.1]) by mail.tcbug.org (Postfix) with ESMTP id 7734C342E62; Mon, 2 Jul 2007 17:21:39 -0500 (CDT) From: Josh Paetzel To: freebsd-questions@freebsd.org, tundra@tundraware.com Date: Mon, 2 Jul 2007 17:22:01 -0500 User-Agent: KMail/1.9.5 References: <468972C5.9090902@tundraware.com> In-Reply-To: <468972C5.9090902@tundraware.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2069888.4zN0L8LJEI"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200707021722.05724.josh@tcbug.org> Cc: Subject: Re: Finally Converting From Bind 8 -> Bind 9 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2007 22:46:00 -0000 --nextPart2069888.4zN0L8LJEI Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 02 July 2007 16:48, Tim Daneliuk wrote: > I am (ever so) slowly moving my domain from FBSD 4.x to 6.2. I am now > at the point where I need to convert my Bind 8 configuration to Bind 9. > In so doing, I like to finally separate my internal (non-routable) hosts > so that their names never resolve outside the private network, and > expose only the public facing hosts to the world via DNS. I'd also > like to (finally) associate names with dhcpd-provided addresses > so both forwards & reverses work inside the private network. > > Could some kind soul please point me to a good HOWTO on this migration and > reconfiguration? I am DAGSing as I write this, but so far have not > found what I want. > > TIA, The first part of what you want is easy.=20 In named.conf you'll have something like... acl private-hosts { 192.168.1.0/24; 192.168.2.0/24; }; view "internal" { match-clients { "private-hosts"; }; zone "example.org" { type master; file "master/db.internal.example.org"; }; }; view "external" { match-clients { any; }; zone "example.org" { type master; file "master/db.example.org"; }; }; Now you have two separate zonefiles, one which is consulted when someone fr= om=20 192.168.1.0/24 or 192.168.2.0/24 makes a query and one that is consulted wh= en=20 anyone else makes a query. HTH =2D-=20 Thanks, Josh Paetzel --nextPart2069888.4zN0L8LJEI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBGiXqNJvkB8SevrssRAkTfAJ9ITkabKpW6XM0PA45hbwfdZc0iGgCfUhgv 18iIJMCOIqAYxtYB3T2eJBs= =iaXx -----END PGP SIGNATURE----- --nextPart2069888.4zN0L8LJEI--