Quoting Steve Litt ([email protected]): [tips about dhclient and resolv.conf:]
> Thanks for the good info. Delighted to help. There's also an interesting thing called 'resolvconf' -- actually, a couple of separate implementations of the idea. It's a piece of software that actively manages the contents of /etc/resolv.conf according to a set of rules you tweak. The naming of the project, though, should serve as a cautionary tale about unwise naming: It's almost imposssible to find the relevant pages in Web search engines, because they're drowned by irrelevant pages about resolv.conf and such. (I've often thought there's good money to be made in selling Internet-obscurity services, helping people and their businesses become deliberately difficult to find on the Net.) Stuff I wrote about that in 2009, elselist: --<begin>-- http://en.wikipedia.org/wiki/Resolvconf http://packages.qa.debian.org/r/resolvconf.html http://roy.marples.name/projects/openresolv The "openresolv" implementation of resolvconf, at least, fully supports Unbound. See: http://roy.marples.name/projects/openresolv/browser/resolvconf.conf.5.in 96 .Sh SUBSCRIBER OPTIONS 97 openresolv ships with subscribers for the name servers 98 .Xr dnsmasq 8 , 99 .Xr named 8 100 and 101 .Xr unbound 8 . Just install your distro's resolvconf package (whatever it's called), and it should notice that you have Unbound running and -- Robert's your father's brother -- make the DHCP client automagically keep its grubby paws off the "nameserver 127.0.0.1" information you wish to retain in /etc/resolv.conf. (Er, there is also the competing, original implementation from Debian developer Thomas Hood called "resolvconf", and I don't know whether it's Unbound-aware or not. Possibly not.[1] If it isn't, file a bug.) [snip] [1] I just got through downloading the latest source tarball from http://ftp.debian.org/debian/pool/main/r/resolvconf/, to check. The README file says, in part: HOWTO ~~~~ Resolvconf works with most interface configurers in Debian ('(*)' below meaning "with some manual configuration"): ppp dhcp3-client, dhcp-client, dhcpcd, pump, udhcpc ifupdown, laptop-net DNS caches: bind9(*), djbdns dnscache, dnsmasq, pdnsd, totd DNS recursing nameservers: bind9(*), pdns-recursor(*) and with any program that uses a DNS client library that consults /etc/resolv.conf to obtain its list of nameservers: the GNU C Library resolver library adns the djbdns resolver library FireDNS That small roster of "DNS recursing nameservers" needs to also gain entries for Unbound, MaraDNS, and dnscache (the recursive part of djbdns). I'll write to Thomas Hood, when I have a moment. --<end>-- _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
