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

[Eygene Ryabinkin]

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