summaryrefslogtreecommitdiff
path: root/net/openresolv
AgeCommit message (Collapse)AuthorFilesLines
2009-12-04Import openresolv-3.3.4roy2-6/+6
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
2009-11-21Import openresolv-3.3.3roy3-7/+8
Changes since 3.3.1 include: * unbound support * documentation updates * more configuration options
2009-06-14Remove @dirrm entries from PLISTsjoerg1-2/+1
2009-05-19Use standard location for LICENSE line (in MAINTAINER/HOMEPAGE/COMMENTwiz1-2/+2
block). Uncomment some commented out LICENSE lines while here.
2009-04-30Update to openresolv-3.3.1roy2-6/+6
Change from 3.3 is dnsmasq now finds extra dbus pidfile locations correctly
2009-04-22Update to openresolv-3.3roy2-6/+6
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.
2009-04-20Add LICENSEroy1-1/+2
2009-04-20Update to openresolv-3.2roy2-6/+6
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.
2009-03-19Update to 3.1.1 to fix a problem with the dnsmasq subscriber.roy2-6/+6
2009-03-18Update to openresolv-3.1roy2-6/+6
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
2009-03-17Use roy@NetBSD.org instead of my personal email.roy1-2/+2
2009-03-16Update to openresolv-3.0roy4-18/+17
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
2009-03-14Update to openresolv-2.1roy4-24/+16
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.
2009-02-07Update to openresolv-2.0.1roy2-6/+7
Fixes metric support and busybox shell sending dbus to dnsmasq.
2008-12-16Satisfy pkglintroy1-1/+6
2008-12-16/etc/resolv.conf is a file that holds the configuration for the localroy5-0/+67
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.