dns-server doesn't create an "rndc.conf" file

[steven-michaud (Steven Michaud)]

It does create an "rndc.key" file in /opt/local/var/named, and adds a "control" to allow rndc to access the bind daemon on ::1 port 54. But rndc won't work without an "rndc.conf" file.

I've had good luck with the following "rndc.conf". It requires that you invoke rndc using sudo, but that should be considered a feature instead of a bug.

include "/opt/local/var/named/rndc.key";
options {
        default-key "rndc-key";
        default-server ::1;
        default-port 54;
};

I'm working on macOS 11.2.3. My MacPorts bind9 distro is "bind9 @9.16.12".

[essandess (Steve Smith)]

Please see ​https://github.com/macports/macports-ports/pull/10342

[essandess (Steve Smith)]

In a64f314af5027bb61029934910664906113c5aa1/macports-ports (master):

dns-server: Update to version 9.16.13 with bugfixes and improvements

• Fixes:
  • #62492
  • #62493
  • #62494
• Minor Portfile formatting improvements

[steven-michaud (Steven Michaud)]

A few hours after this bug's fix landed (as per comment 3) I tested it as follows:

1. I ran sudo port selfupdate and sudo port upgrade outdated to make sure I had the latest version of everything MacPorts.

2. I sudo port uninstalled both dns-server and bind9. I also removed all the files dns-server had created.

3. I reran sudo port install dns-server.

The fix worked. An appropriate rndc.conf file had been created in /opt/local/etc.

Thanks for fixing this so quickly!

[essandess (Steve Smith)]

This issue is fixed by ​https://github.com/macports/macports-ports/pull/10342 and may be closed.