From owner-freebsd-current@FreeBSD.ORG Fri Apr 25 15:53:16 2008 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 46BF7106566B for ; Fri, 25 Apr 2008 15:53:16 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id D67C68FC21 for ; Fri, 25 Apr 2008 15:53:15 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=RoDB3HlrweoBgXdXuk006/cG9PTJDRtgesmFYcd3V9u3FYgbyHLHz2NVi7fLVCbsq5weeFz3azyCbj4OP0i1NpsxIdqS0NrnZ+AQO5RGYRkYQVQxRXhIO0f/jnEE1h2UisqAZugZinyTPFaDT3U9uCJ9lxppva6aCtCLuIYysgU=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1JpQEc-0001U9-85; Fri, 25 Apr 2008 19:53:14 +0400 Date: Fri, 25 Apr 2008 19:53:13 +0400 From: Eygene Ryabinkin To: John Baldwin Message-ID: References: <200804240821.40601.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200804240821.40601.jhb@freebsd.org> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-2.1 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_20 Cc: Poul-Henning Kamp , freebsd-current@freebsd.org 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 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Apr 2008 15:53:16 -0000 John, good day. Thu, Apr 24, 2008 at 08:21:40AM -0400, John Baldwin wrote: > You can already override the domain name and DNS servers (including either > overriding, providing a default, or prepending or appending to the list) via > setings in /etc/dhclient.conf, so I don't think new rc.conf variables for > that would be warranted. In the case of DHCP -- yes, I can. But sometimes I need to specify the static entries for the resolv.conf: I am using it when I am working in some places where DHCP isn't available, so I am creating branched /etc/rc.conf. And it is useful to have all variables in one place. For my usage, dhclient.conf is not relevant, since I am happily taking all that was given me via DHCP. > Updating named.conf to forward is a neat idea. > Howver, on my laptop on HEAD I've ended up just running nscd instead of a > local DNS server and doing a 'nscd -I hosts' when I get a new lease to flush > the host cache. When I get to my laptop I'll post my bits of > dhclient-exit-hooks and dhclient.conf to make this work. Yes, it is also the way to go, but, at was said by Poul-Henning, nscd is not so smart to know all particulars of DNS, namely -- the different TTL values for the different records and zones. May be I can integrate the usage of the nscd to the dhclient-script and rc.conf? Is it desirable? -- Eygene