Bind has switched terminology from master/slave to primary/secondary. https://bind9.readthedocs.io/en/v9_16_12/introduction.html?highlight=primary#the-primary-server When using this more modern terminology it makes sense to also change the names of the directories 'master' and 'slave' to 'primary' and 'secondary', which I did. I would appreciate it if the make options for the port could include options like (*) Use primary/secondary terminology ( ) User master/slave terminology This would avoid the creation of new directories named 'master' and 'slave' when updating, as well as the installation of new 'empty.db' and 'localhost-*.db' files in unused directories. On the other hand, it would still allow existing installations to continue using the old terminology, if desired. Since Bind now prefers the use of primary/secondary, it would probably also make sense to use these terms as the default for new installs. Thanks, Rob
BIND9 already has way too many options, adding a new option for this seems like a bad idea. I am going to have a look on how to make the change transparent for the users, it will probably only happen in bind9-devel for now, and it will probably only happen in the new versions of BIND9 ports, starting with the next 9.18 version.
Migrated to primary/secondary in the latest bind9-devel port.
A commit references this bug: Author: mat Date: Mon Mar 15 16:09:08 UTC 2021 New revision: 568467 URL: https://svnweb.freebsd.org/changeset/ports/568467 Log: Update to latest commit. While there, transition from master/slave to primary/secondary in the default configuration files. PR: 253799 Changes: head/dns/bind9-devel/Makefile head/dns/bind9-devel/distinfo head/dns/bind9-devel/files/BIND.chroot.local.dist head/dns/bind9-devel/files/named.conf.in head/dns/bind9-devel/files/pkg-message.in head/dns/bind9-devel/pkg-plist