From owner-freebsd-stable@FreeBSD.ORG Tue Jul 17 23:00:28 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 994AA16A401 for ; Tue, 17 Jul 2007 23:00:28 +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 284FC13C4B2 for ; Tue, 17 Jul 2007 23:00:28 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.37] (a89-182-28-88.net-htp.de [89.182.28.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id AB702A44529; Wed, 18 Jul 2007 00:58:52 +0200 (CEST) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: Doug Barton , Volker , freebsd-stable@freebsd.org Date: Wed, 18 Jul 2007 01:00:25 +0200 User-Agent: KMail/1.9.7 References: <200707162319.41724.lofi@freebsd.org> <469D2E40.5020707@FreeBSD.org> <20070717210622.GA89814@eos.sc1.parodius.com> In-Reply-To: <20070717210622.GA89814@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200707180100.26152.wundram@beenic.net> Cc: 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 23:00:28 -0000 On Tuesday 17 July 2007 23:06:22 Jeremy Chadwick wrote: > Can you expand on this, re: why it's "bad advice"? I also cannot make > heads or tails of the BIND ARM saying it's "not recommended". Please > shed some light on this for those of us less experienced in the know, > if you could (I mean that sincerely). See my mail: <200707171410.41601.wundram@beenic.net>, also in this thread. A stub zone is basically a zone that's only configured with an absolutely=20 necessary amount of records (for the _zone_ itself). The idea behind stub=20 zones is the following: $ORIGIN modelnine.org stubzone IN NS ns1.stubzone How is stubzone ever going to be resolvable unless you specify glue for=20 ns1.stubzone.modelnine.org? Normally, the standard "way" of doing this woul= d=20 be to set up a glue (A) record for ns1.stubzone in modelnine.org, but with= =20 stub zones you can also create different zone files: $ORIGIN modelnine.org $ORIGIN stubzone.modelnine.org IN NS ns1 ns1 IN A a.b.c.d which you can then integrate into your bind configuration as a normal zone = for=20 modelnine.org and as a stub zone for stubzone.modelnine.org, and which only= =20 contains the glue necessary to have the subdomain/-zone working by itself,= =20 but does not contain other records. When the nameserver sees a stub zone, it will not take the content of the z= one=20 file as "authoritative" on existance or non-existance of domain names in th= at=20 zone, but only uses the records in the zone as glue or nameserver definitio= ns=20 which are necessary to run the lookup to the "true" zone behind the stub,=20 which are then normally resolved. So, basically, this is a (different) way = of=20 defining glue, which I personally don't find very appealing, as it splits t= he=20 glue over many, many files. This mechanism is simply not applicable to the situation this thread was=20 talking about (using the root zone as hint or slave), that's what Doug was= =20 trying to say, and I was trying to say in the mail I hinted at above. =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