From owner-freebsd-current@FreeBSD.ORG Fri Dec 14 18:39:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 112B316A419 for ; Fri, 14 Dec 2007 18:39:16 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id 7D86713C47E for ; Fri, 14 Dec 2007 18:39:15 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so1457827uge.37 for ; Fri, 14 Dec 2007 10:39:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; bh=9uwpmWS1TIqlIzlMMRIR+z+V83xjPl9kybVpBc3Rxa8=; b=kaeJZ2HPnyQHoixcb+aJbOsroHAwvf5wMupzMN+RDVEjxFBKXKsqxTRFPDVzJPWxrJQAqRitgA0V/2F/ltvqU7DCwug0bc32njif2xTxkZCP+31zZn5Keyqml0xg49CyK7lX6I8UukyGte5jt8iPo2tzBR93Lo2RIQtiSs9X74w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=dXDj5cwzUic+WAhry+t812ghXdrfhbvU4YcacIYPnep3AT865n+NyPjbZHEBrRJ2SluWUWogcAi5MMEJ9Jk/BGFxAubLcYhNbr/vHZp2wy1unvfLvXT7TNwWPJq3t+VE/WMS12088QLUdsDbi84lOHkeQnJGpLuHzYh1omsvrAQ= Received: by 10.78.162.4 with SMTP id k4mr4589700hue.66.1197657553633; Fri, 14 Dec 2007 10:39:13 -0800 (PST) Received: from orion ( [89.162.141.1]) by mx.google.com with ESMTPS id y6sm22384570mug.2007.12.14.10.39.09 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 14 Dec 2007 10:39:10 -0800 (PST) From: Nikolay Pavlov To: freebsd-current@freebsd.org Date: Fri, 14 Dec 2007 20:39:07 +0200 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) References: <72389.1197629858@critter.freebsd.dk> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4613370.M3EtAJ3uH5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200712142039.07590.qpadla@gmail.com> Cc: Poul-Henning Kamp Subject: Re: [RFC] Automated generation of /etc/resolv.conf from the rc.d script X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Dec 2007 18:39:16 -0000 --nextPart4613370.M3EtAJ3uH5 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 14 December 2007 13:07:00 Eygene Ryabinkin wrote: > Fri, Dec 14, 2007 at 10:57:38AM +0000, Poul-Henning Kamp wrote: > > In message ,=20 Eygene Ryabinkin writes: > > >> It should be possible to run a local named even when we run DHCP, > > >> and it shuld be an option, to have it automatically forward to the > > >> DNS servers we learn from DHCP. > > > > > >This can be achieved with the script /etc/dhclient-exit-hooks that > > >will create the file with named 'forwarders' clause [...] > > > > Yes, I know that, but I would like to see it controllable from rc.conf > > like the rest of our network configuration. > > OK, since running local DNS instance is a neat idea, I will try to > draft the modifications for the dhclient-exit-hooks, as I described > in the previous mail. > > Just now I see no other way to implement it, because dhclient is > asynchronious in the general case, so I can not teach /etc/rc.d/dhclient > to do the job. So I expect that /etc/dhclient-exit-hooks will be > born and it will build 'forwarders' file for the named, if this > will be requested by /etc/rc.conf. > > I still not sure how to modify named.conf: automatically or let the > user make the needed modifications. I am inclined to the latter, > but this can pose some troubles to the users that are not very > familiar with named.conf. Any thoughts? > > If you have other ideas how it can be done, please share. > > Thanks! Hi Eygene. You might get some ideas from this implementation then: http://packages.debian.org/sid/resolvconf At least it contains those ugly sed expression to edit forwarders in a=20 named.conf. =2D-=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =2D Best regards, Nikolay Pavlov. <<<----------------------------------- = =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 --nextPart4613370.M3EtAJ3uH5 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHYs3L/2R6KvEYGaIRAlodAKCsSqxJredmVMMfMSH+55I5untrwgCePciL aPHcI0rNXxJfzhI31Dw8N8Y= =uwjR -----END PGP SIGNATURE----- --nextPart4613370.M3EtAJ3uH5--