<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span style="font-family: Menlo-Regular; font-size: 13px;" class="">Sorry to probably ask the obvious but what command do I use to start it manually?</span><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 22 Sep 2022, at 15:27, Daniel J. Luke <<a href="mailto:dluke@geeklair.net" class="">dluke@geeklair.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">On Sep 22, 2022, at 8:56 AM, Mark Lucas <<a href="mailto:mark@arc.co.uk" class="">mark@arc.co.uk</a>> wrote:<br class="">I just updated to bind 9.18.7 (Intel mac mini - macOS 12.6 ) and despite checking the config was ok, which it was, bind refuses to start. <br class="">Looking at the contents of /opt/local/var/named/ mysteriously most of the files were now listed as being owned by non existent user 511. <br class="">e.g. -rw-r--r-- 1 511 named - 3.2K 4 Aug 2021 named.root<br class="">Tried uninstalling and reinstalling bind9 and changing /opt/local/var/named/ files owner to named but the problem remains.<br class=""></blockquote><br class="">I think the permissions stuff is unrelated to the port - it only installs these files into /opt/local/var/named:<br class=""><br class="">% port contents bind9 | grep /opt/local/var/named<br class=""> /opt/local/var/named/db.127.0.0.dist<br class=""> /opt/local/var/named/db.cache.dist<br class=""> /opt/local/var/named/db.localhost.dist<br class=""><br class="">You can try to start named by hand with `-g` (and maybe add a -d # option) to try to get more information on why it's not starting for you.<br class=""><br class="">-- <br class="">Daniel J. Luke<br class=""><br class=""></div></div></blockquote></div><br class=""></body></html>