From owner-freebsd-stable@FreeBSD.ORG Tue Jul 17 15:40:42 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 919A216A409 for ; Tue, 17 Jul 2007 15:40:42 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 2FC2D13C4AC for ; Tue, 17 Jul 2007 15:40:41 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 20821 invoked by uid 399); 17 Jul 2007 15:40:41 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 17 Jul 2007 15:40:41 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <469CE2F7.2000402@FreeBSD.org> Date: Tue, 17 Jul 2007 08:40:39 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.4 (X11/20070617) MIME-Version: 1.0 To: Michael Nottebrock References: <200707162319.41724.lofi@freebsd.org> <200707170920.24692.lofi@freebsd.org> <200707170931.57751.wundram@beenic.net> <200707171030.05604.lofi@freebsd.org> In-Reply-To: <200707171030.05604.lofi@freebsd.org> X-Enigmail-Version: 0.95.1 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Heiko Wundram \(Beenic\)" , freebsd-stable@freebsd.org Subject: Re: Problems with named default configuration in 6-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2007 15:40:42 -0000 Michael Nottebrock wrote: > On Tuesday, 17. July 2007, Heiko Wundram (Beenic) wrote: >> This is natural, unless you specifically enter the zones for 192.168.8.* >> (forward and reverse) in your client DNS server (as slave or forward zones, >> see the bind manual for the latter, which I'd recommend in your case). Yes, this is the right answer. Thanks Heiko for providing it. BIND always takes more specific zone definitions first before less specific ones. So if using your example you set a zone for 8.168.192.in-addr.arpa named will first look up names in that zone, and anything else in 168.192.in-addr.arpa that isn't in that zone will get the local NXDOMAIN answer. Same rules apply for forward zones of course (to named there is no difference, a zone is a zone). I think this issue probably deserves a comment in the named.conf file. I'll prepare a patch and send it to re@. > Ah, I'm (re)-learning more about DNS here than I ever thought I would. Indeed, > with forward and reverse slave zones, I don't need to comment out anything > anymore from the default config. I guess that solves my problems and the list > audience will be saved from yet more DNS talk. :) Heh, well I'm glad it worked out for you, and I'm sorry I missed your initial message, I could have saved a lot of drama if I'd left the office 15 minutes later. :) Doug -- This .signature sanitized for your protection