Re: [RFC] Automated generation of /etc/resolv.conf from the rc.d script

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