dnscache-run modifies /etc/resolv.conf. So do several other packages.
All these packages overwrite one another's changes. That is bad.
The resolvconf package was created in order to resolve this and related
problems. Resolvconf allows packages to add information to the resolver
configuration file without conflicting with one another. See the
resolvconf package's README for a full explanation.
Most caching nameservers are compatible with resolvconf but dnscache-run
is not (yet).
If everyone agrees then I will retitle this report "Please make
dnscache-run compatible with resolvconf" and, if needed, provide more
information about how to make dnscache-run compatible with resolvconf.
That's a *wish*. The only real *bug* at present is the fact that
dnscache-run conflicts with every other package that writes to
/etc/resolv.conf, including resolvconf. In order to deal with this from
the resolvconf end of things I will add a Conflicts: dnscache-run to the
next release of resolvconf.
The issue of whether any package has the right to alter /etc/resolv.conf
is an issue affecting several packages and should be discussed on
debian-devel before any bug reports are filed. Note that resolvconf
does not write to /etc/resolv.conf but to a file under /lib/init/rw/ to
which /etc/resolv.conf is symlinked.
--
Thomas Hood
Member of the resolvconf maintainers team
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
