Yesterday, I wrote about the local caching resolver we now have in FreeBSD 10. I’ve fielded quite a few questions about it (in email and on IRC), and I realized that although this has been discussed and planned for a long time, most people outside the 50 or so developers who attended one or both of the last two Cambridge summits (201208 and 201308) were not aware of it, and may not understand the motivation.
There are two parts to this. The first is that BIND is a support headache with frequent security advisories and a lifecycle that aligns poorly with our release schedule, so we end up having to support FreeBSD releases containing a discontinued version of BIND. The second part is the rapidly increasing adoption of DNSSEC, which requires a caching DNSSEC-aware resolver both for performance reasons (DNSSEC validation is time-consuming) and to avoid having to implement DNSSEC validation in the libc resolver.
We could have solved the DNSSEC issue by configuring BIND as a local caching resolver, but for the reasons mentioned above, we really want to remove BIND from the base system; hence the adoption of a lightweight caching resolver. An additional benefit of importing LDNS (which is a prerequisite for Unbound) is that OpenSSH can now validate SSHFP records.
Note that the dns/unbound port is not going away, and that users who want to run Unbound as a caching resolver for an entire network rather than just a single machine have the option of either moving their configuration into
/var/unbound/unbound.conf, or running the base and port versions side-by-side. This should not be a problem as long as the port version doesn’t try to listen on
I’d like to add that since my previous post on the subject, and with the help of readers, developers and users, I have identified and corrected several issues with the initial commit
/etc/unboundis now a symlink to
/var/unbound. My original intention was to have the configuration files in
/etc/unboundand the root anchor,
unbound-controlkeys etc. in
/var/unbound, but the daemon needs to access both locations at run-time, not just on start-up, so they must all be inside the chroot. Running the daemon un-chrooted is, of course, out of the question.
- The init script ordering has been amended so the
local_unboundservice now starts before most (hopefully all) services that need functioning DNS.
resolvconf(8)is now blocked from updating
/etc/resolv.confto avoid failing over from the DNSSEC-aware local resolver to a potentially non-DNSSEC-aware remote resolver in the event of a request returning an invalid record.
configurecommand line and date / time are no longer included in the binary.
Finally, I just flipped the switch so that BIND is now disabled by default and the LDNS utilities are enabled. The
LDNS_UTILS build options are mutually exclusive; in hindsight, I should probably have built and installed the new
ldns-host(1) so both options could have been enabled at the same time. We don’t yet have a
dig(1) wrapper for
host(1) is the only actual conflict.