FreshPorts -- dns/bind9-devel: BIND DNS suite with updated DNSSEC and DNS64

bind9-devel
ABI	latest	quarterly
FreeBSD:11:aarch64	9.13.1.a0.2018.09.20_1	9.17.0.a0.2020.06.23
FreeBSD:11:amd64	9.17.8.a0.2021.01.04	9.17.7.a0.2020.11.27
FreeBSD:11:armv6	9.11.0.a20160620	-
FreeBSD:11:i386	9.17.8.a0.2021.01.04	9.17.7.a0.2020.11.27
FreeBSD:11:mips	9.12.0.a.2016.07.04	-
FreeBSD:11:mips64	9.12.0.a.2016.07.04	-
FreeBSD:12:aarch64	9.13.1.a0.2018.09.28_1	9.17.7.a0.2020.11.27
FreeBSD:12:amd64	9.17.8.a0.2021.01.04	9.17.7.a0.2020.11.27
FreeBSD:12:armv6	9.13.1.a0.2018.09.28_1	-
FreeBSD:12:armv7	9.13.1.a0.2018.10.05_1	-
FreeBSD:12:i386	9.17.8.a0.2021.01.04	9.17.7.a0.2020.11.27
FreeBSD:12:mips	-	-
FreeBSD:12:mips64	-	-
FreeBSD:12:powerpc64	-	9.17.7.a0.2020.11.27
FreeBSD:13:aarch64	9.17.8.a0.2021.01.04	-
FreeBSD:13:amd64	9.17.8.a0.2021.01.04	-
FreeBSD:13:armv6	-	-
FreeBSD:13:armv7	-	-
FreeBSD:13:i386	9.17.8.a0.2021.01.04	-
FreeBSD:13:mips	-	-
FreeBSD:13:mips64	-	-
FreeBSD:13:powerpc64	-	-

Reason: This is only for FreeBSD 10.0+. BIND auto chroot has been added back to the named rc script. As enabling it by default would most certainly break people's setup, it is not. To enable it, and chroot it in /var/named, add the following line to your rc.conf file: named_chrootdir="/var/named" On first launch, the rc script will move the /usr/local/etc/namedb directory into the chroot, and create a symlink to it. Note that, if you're running from within a jail, you need to have a /var/named/dev devfs created beforehand, with the null and random devices.

Reason: All bind9 ports have been updated to support FreeBSD 10.x after BIND was removed from the base system. It is now self-contained in ${PREFIX}/etc/namedb, and chroot and symlinking options are no longer supported out of the box. For users of FreeBSD 9.x and earlier, the LINKS option is no longer enabled by default, but still supported. No other changes should affect those users, and updating without changing already set options will keep the system in the same state.

Enabled DNSTAP by default. The ISC recommends having it by default (it is in the packages they distribute) and the footprint of the dependecies is very small. While there, cleanup plists. PR: 237861 Reported by: Greg Rivers

Update to latest commit. While there, move named-journalprint from bind-tools to bind9, it is only useful on machines with BIND9 running, where journal files actually exist. The man page was already in the correct port.

Fix named when using plugins and chroot. BIND9 introduced plugins and migrated the filter-aaaa feature to a plugin. As it loads its plugins late in the startup process (read after chroot), the plugins need to be available in the chroot. Also, refactor the code now that a second directory need to be handled. PR: 238011 Reported by: ryan@timewasted.me MFH: 2019Q2

Remove conflicts from bind-tools and the server ports. All servers now depend on the same bind-tools, from the latest BIND9 release. Chase dependencies to make sure they now depend on the correct port. Differential Revision: https://reviews.freebsd.org/D19922

Current status