bind9 macOS High Sierra

[tigerkr]

Upgraded from El Cap to High Sierra. Followed macports migration instructions. DHCPD works just fine, but bind9 / named does not:

Nov  1 06:47:42 localhost com.apple.xpc.launchd[1] (org.macports.bind9): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

I've tried using launchctl to unload and reload to no avail. The respawn keeps spamming /var/log/system.log

[tigerkr]

I installed homebrew, and the homebrew port works just fine.

[mf2k (Frank Schima)]

In the future, please use WikiFormatting and Cc the port maintainers (port info --maintainers bind9), if any.

[danielluke (Daniel J. Luke)]

What happens if you run sudo /opt/local/sbin/named -u named -f

[tigerkr]

I've just nuked and paved my server. But I ran across the same issue upon reinstall.

# sudo /opt/local/sbin/named -u named -f

# isc_stdio_open '/var/log/named.log' failed: permission denied

So I issued the following commands:

# sudo touch /var/log/named.log

# sudo chown named:named /var/log/named.log

Now it seems to be running. You may want to fix this in the install, either in the script, or in the instructions.

[danielluke (Daniel J. Luke)]

Can you upload your named.conf file? The default file doesn't include logging to /var/log/named.log so you shouldn't be seeing this error.

[tigerkr]

You are correct, I do apologize. I have a marked up named.conf that I've been using for years.

logging {
 
        channel default {
                file "/var/log/named.log";
                severity info;
                print-category yes;
                print-severity yes;
                print-time yes;
        };
 
        channel named_syslog {
                syslog daemon;
                severity info;
                print-category yes;
                print-severity yes;
                print-time yes;                                                 
        };
 
 
        category default        { default; named_syslog; }; 
        category config         { default; };
        category queries        { null; };
        category lame-servers   { null; };
        category update         { default; };
        category xfer-in        { default; };
        category xfer-out       { default; };
        category notify         { default; };                              
        category security       { default; };
};

[danielluke (Daniel J. Luke)]

ok, so the error is coming because you're specifically set up bind9 to log to a file/directory where it doesn't have write permission (ie, this is not the conf that we ship with the port).

For what it's worth, when I run bind9, I create a /var/log/named/ directory owned by the 'named' user where it can log (and store multiple log 'versions').

If you'd like to suggest adding some default logging to the port, I'd welcome a patch - but it doesn't look like you've found a bug with the port at this point.