openrsolv development is moving to

IF you have any tickets here, please re-create them at the new site!

openresolv - the DNS management framework

/etc/resolv.conf is a file that holds the configuration for the local resolution of domain names. Normally this file is either static or maintained by a local daemon, normally a DHCP daemon. But what happens if more than one thing wants to control the file? Say you have wired and wireless interfaces to different subnets and run a VPN or two on top of that, how do you say which one controls the file? It's also not as easy as just adding and removing the nameservers each client knows about as different clients could add the same nameservers.

Enter resolvconf, the middleman between the network configuration services and /etc/resolv.conf. resolvconf itself is just a script that stores, removes and lists a full resolv.conf generated for the interface. It then calls all the helper scripts it knows about so it can configure the real /etc/resolv.conf and optionally any local nameservers other than libc.

Reasons for using openresolv

Why openresolv over the Debian implementation? Here's some reasons

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 will go to and queries for will go to 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

See the configuration section for more details.


openresolv is released under the 2 clause BSD license.

You can find a distinfo (.distinfo) file and GPG signature (.distinfo.asc) for newer releases alongside the released archive.
GPG Fingerprint: A785 ED27 5595 5D9E 93EA 59F6 597F 97EA 9AD4 5549