* Save the initial working directory and change to it just before
running any scripts.
This avoids scripts putting files accidently where they shouldn't.
* Strip trailing dot from search and domain names.
* man page improvements.
* Typo's, thanks to Herbert Parentes Fortes Neto
* Clarify that private_interfaces="*" will not forward the root zone
* Change from bzip2 to xz for builiding the source tarball
* ensure that domain-insecure always appears in a server clause for
the unbound subscriber
Changes from openresolv-3.3.3 include:
* private_interfaces is now shell expandable (ie, fxp*)
* dnsmasq resolver restarting with DBus is now fixed
* unbound resolver is sent SIGHUP for reload instead of forced restart
* subscribers with the execute bit are executed, otherwise sourced into
a subshell for speed
Changes from 3.2 include
* Logic to restart each service is now embedded in subscribers at
compile time, which reduces runtime code size.
This is also configurable in resolvconf.conf.
* If subscribers are called from resolvconf, they no longer re-execute it
to get the data they need.
This saves on a lot of forking and as a result a fair bit faster.
* A bug was fixed in the dnsmasq susbcriber where the domain name servers
weren't used correctly.
Changes from 3.1.1 include
* resolv_conf_passthrough makes the libc subscriber just copy the latest
resolv.conf to \$resolv_conf
* private_interfaces allows resolv.conf nameservers to be private for the
domains in the same file. Requires a resolver other than libc.
Changes since 3.0:
* New variable dynamic_order
* interface processing now interface_order, dynamic order without metric,
metric and and everything else in lexical order
No functional changes since 2.x, but the configuration has moved from
lots of little configuration files into one easier to manage configuration
file with a nice man page - resolvconf.conf
No functional changes since 2.0.1 aside from moving the shell scripts
out of etc and into libexec.
The configuration files in etc/resolvconf/resolv.conf.d have been moved into
resolvconf.
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 can libc.
