From owner-freebsd-stable@FreeBSD.ORG Tue Jul 17 08:04:46 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 06D0916A406 for ; Tue, 17 Jul 2007 08:04:46 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from mail.beenic.net (mail.beenic.net [83.246.72.40]) by mx1.freebsd.org (Postfix) with ESMTP id 8AE4913C47E for ; Tue, 17 Jul 2007 08:04:45 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.37] (a89-182-2-214.net-htp.de [89.182.2.214]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id 1CDE1A44529 for ; Tue, 17 Jul 2007 09:30:26 +0200 (CEST) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: freebsd-stable@freebsd.org Date: Tue, 17 Jul 2007 09:31:57 +0200 User-Agent: KMail/1.9.7 References: <200707162319.41724.lofi@freebsd.org> <20070717052823.GA1277@darklight.org.ru> <200707170920.24692.lofi@freebsd.org> In-Reply-To: <200707170920.24692.lofi@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200707170931.57751.wundram@beenic.net> 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 08:04:46 -0000 On Tuesday 17 July 2007 09:20:16 Michael Nottebrock wrote: > Yes - and this: > > zone "." { > type slave; > file "slave/root.slave"; > masters { > 192.5.5.241; // F.ROOT-SERVERS.NET. > 192.228.79.201; // B.ROOT-SERVERS.NET. > 192.33.4.12; // C.ROOT-SERVERS.NET. > 192.112.36.4; // G.ROOT-SERVERS.NET. > 193.0.14.129; // K.ROOT-SERVERS.NET. > }; > notify no; > }; > > prevents me from resolving hostnames in "my.domain". What I'm still > wondering though, is this an oversight or by design? I can't imagine setu= ps > like mine are very rare. Doug? This is natural, unless you specifically enter the zones for 192.168.8.*=20 (forward and reverse) in your client DNS server (as slave or forward zones,= =20 see the bind manual for the latter, which I'd recommend in your case). The explanation is simple: how is (your local) bind supposed to know which= =20 server to query for those domains, as the (public internet) root name serve= rs=20 won't reply for them (zones always take precedence over forwarders, so if y= ou=20 have a zone for ".", i.e. everything, in your named.conf, your forwarder is= =20 never queried for anything), and it has no other info on=20 8.168.192.in-addr.arpa than to resursively look it up starting from a root= =20 name server, which won't answer but with a NXDOMAIN response. If you remove the hints, there's only a forwarder left in your configuratio= n,=20 which in turn is always queried, and which can also properly resolve your=20 domains. Hope this explains stuff. =2D-=20 Heiko Wundram Product & Application Development =2D------------------------------------ Office Germany - EXPO PARK HANNOVER =20 Beenic Networks GmbH Mail=E4nder Stra=DFe 2 30539 Hannover =20 =46on +49 511 / 590 935 - 15 =46ax +49 511 / 590 935 - 29 Mail wundram@beenic.net Beenic Networks GmbH =2D------------------------------------ Sitz der Gesellschaft: Hannover Gesch=E4ftsf=FChrer: Jorge Delgado Registernummer: HRB 61869 Registergericht: Amtsgericht Hannover