From owner-freebsd-current@FreeBSD.ORG Wed Apr 23 14:36:21 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 387621065673; Wed, 23 Apr 2008 14:36:21 +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 AF78C8FC13; Wed, 23 Apr 2008 14:36:20 +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=N8Dpz3iM3Dq5KMc2NO3m//ZJWMeH4v5YoxySSGspocRM6HqPfXIXBTZ3nG1pVYftmDyWSpR1FarRNLn5VvNR3tDISRqtziI3GN3GpcQVgF/eOZXiGJn6mGbdN5Its0h5VTiV6cNTDg5rnrLLN5yUXCNYZPEMTRP/dEN+swW/LYI=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1Jog55-0009gc-03; Wed, 23 Apr 2008 18:36:19 +0400 Date: Wed, 23 Apr 2008 18:36:17 +0400 From: Eygene Ryabinkin To: Brooks Davis , Poul-Henning Kamp Message-ID: <+rkPaEJgDwWM+WmNdLneOfPN6Ps@sTlCVUsSEVReKIVdz1gJKNXWeKE> References: <72123.1197626129@critter.freebsd.dk> <5f67a8c40804141026s27672065sb11a7f327572c0f2@mail.gmail.com> <5f67a8c40804141044v69557b92w7db0b272d6b9b848@mail.gmail.com> <3BdnONI1bT08mgV1Is+vnPQaMNw@OG4t+/sM8WGI7cjjTW4/N4fcF6w> <20080421162612.GA19629@lor.one-eyed-alien.net> <20080422204510.GB34198@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <12763.1208898696@critter.freebsd.dk> <20080422204510.GB34198@lor.one-eyed-alien.net> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-2.3 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_05 Cc: Zaphod Beeblebrox , 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: Wed, 23 Apr 2008 14:36:21 -0000 Brooks, Poul-Henning, good day. > This looks like useful functionality to me. I have't had time to dig in > in detail. Could you please submit it as a PR so it doesn't get lost? OK, will do. Tue, Apr 22, 2008 at 09:11:36PM +0000, Poul-Henning Kamp wrote: > >By the way, do you have some thoughts about the patches I had sent? > >Or you just don't need such functionality? I am not receiving any > >comments, so does it mean that these patches are unneeded? Anyone? > >Poul-Henning? > > I think this is a much needed facility. Some ISP's block DNS queries > from private customers to force them to use the ISP's DNS and > not having this forces a cumbersome manual configuration. Hmm, my patch does not change anything in the respect to the ISP's DNS servers: resolv.conf or BIND will use the nameservers given by DHCP or manually configured via /etc/rc.conf. For the DHCP case this coincides with the current behaviour: dhclient creates /etc/resolv.conf with the obtained DNS servers. But sure, the case of a local BIND instance is not covered by the current configuration, but is handled in the patch. To summarize, the useful functionality, as I see it, is the following. a) One can build /etc/resolv.conf programmatically via variables in rc.conf; I am using it to implement multiple configurations for my notebooks. b) One can have local BIND instance caching the answers from the upstream forwarders and it is automatically (re)configured by DHCP or /etc/rc.conf when upstream DNS servers list is changed. Very handy when you're sitting on the lossy link, having temporary connectivity problems and is generally saving some DNS-related traffic. Thanks for your opinions! -- Eygene