CVS log for pkgsrc/net/openresolv/PLIST

Up to [cvs.NetBSD.org] / pkgsrc / net / openresolv

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

Update to openresolv-3.16.2 with the following changes:

 * unbound: allow maring doamins as private
 * resolvconf: exclude option an exclude a whole file
 * resolvconf: allow -p to list private entries without -a
 * resolvconf: support subscribers with a dash in their name
 * systemd-resolved: now supported for global nameservers only
 * resolvconf: -L now outputs fully processed entries
 * resolvconf: domains are normalised to lowercase
 * libc: don't restore resolv.conf.bak when resolv.conf is empty

Update to openresolv-3.11.0 with the following changes:

  *  notify avahi-daemon of resolv.conf being changed
  *  notify mdnsd of resolv.conf being changed

Import openresolv-3.9.2 with the following changes:
*  dnsmasq: clear cache after updating servers via dbus
*  pdns_recursor: Fix global forwards (thus now installed by default)
*  man: layout and misc fixes

Import openresolv-3.4.0 with the following changes
* pdnsd support
* Ability to append to the search domains

Import openresolv-3.3.3
Changes since 3.3.1 include:
* unbound support
* documentation updates
* more configuration options

Remove @dirrm entries from PLISTs

Update to openresolv-3.0

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

Update to openresolv-2.1

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.

/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 can libc.

Initial revision