The state of resolv.conf

[Adam Tkac]

On Tue, Sep 16, 2008 at 05:01:29AM -0500, Callum Lerwick wrote:
> On Mon, 2008-09-15 at 08:44 -0400, Simo Sorce wrote:
> > On Mon, 2008-09-15 at 09:32 +0200, Ahmed Kamal wrote:
> > > Wouldn't the best way be to have an api that can be used to add and
> > > delete DNS servers and manipulate resolv.conf. Then we could have
> > > deamons call that.
> > 
> > No what you really need is more than a simple resolv.conf file.
> > 
> > We need a default caching daemon (which by itself will solve a lot of
> > other issues) that tools like NM, vpnc, openvpn can interact with.
> > These tools will tell the caching daemon which IP ranges and which
> > domains their provided forwarders should be consulted for. All dynamic
> > so that as soon as one daemon goes away, the caching DNS will notice and
> > revert queries to the default DNS. And if NM/routes go away it can keep
> > working out of its cache.

If NM and routes go away I think you don't need DNS at all ;)

If you are interested only in caching why you cannot use nscd?

I have creation of NM support to BIND in TODO
(https://bugzilla.redhat.com/show_bug.cgi?id=441057) but I haven't got
time for it yet. If vpnc/openvpn will interract with NM then you can ask
NM for DNS servers for every interface and then use them as "forwarders"
in BIND. Additionaly you can get advantage of DNSSEC aware resolver.

Adam

-- 
Adam Tkac, Red Hat, Inc.