Re: Bug#595081: ITP: openresolv -- management framework for resolv.conf
On Tue, 2010-08-31 at 15:20 -0700, Don Armstrong wrote:
> On Tue, 31 Aug 2010, Roy Marples wrote:
> > Description : management framework for resolv.conf
> > Allows multiple daemons to manage resolv.conf and configures local
> > resolvers such as dnsmasq and unbound.
> How does this differ from resolvconf which already has significant
> buy-in and integration in Debian?
* Works with POSIX shell and userland
* Does not need awk, grep or sed which means we can work
without /usr mounted
* Works with other init systems than Debians' out of the box
* Available as a 2 clause BSD license
* Prefer configs via IF_METRIC for dynamic ordering
* Configures zones for local resolvers other than libc
The last point is quite important, especially when running VPN systems.
Take the following resolv.conf files which have been generated by a
DHCP client and sent to resolvconf:
# resolv.conf from bge0
# resolv.conf from tap0
In this instance, queries for foo.com will go to 126.96.36.199 and queries for
bar.org will go to 188.8.131.52. This does require the resolvers to be
configured to pickup the resolvconf generated configuration for them
though. openresolv ships with helpers for dnsmasq, ISC BIND,PowerDNS
Recursor and unbound
Other than that, the openresolv is command line compatible with
resolvconf. However, the setup is not. Instead of many directories and
files to manage, openresolv just uses /etc/resolvconf.conf.
Aside from the user specific configuration, openresolv integrates 100%
with a Debian based system.