Big Sur on M1 - bind9 named daemon don't run

[Bill Cole]

On 2022-09-22 at 10:27:16 UTC-0400 (Thu, 22 Sep 2022 10:27:16 -0400)
Daniel J. Luke <dluke at geeklair.net>
is rumored to have said:

>> On Sep 22, 2022, at 8:56 AM, Mark Lucas <mark at arc.co.uk> wrote:
>> 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.
>> 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.
>> e.g. -rw-r--r--   1 511    named  -           3.2K  4 Aug  2021 
>> named.root
>> Tried uninstalling and reinstalling bind9 and changing 
>> /opt/local/var/named/ files owner to named but the problem remains.

named.root is the historical name of the root cache for BIND. Identical 
to what MacPorts installs as db.cache.dist. The directory 
/opt/local/var/named/ and everything in it should be owned by user and 
group 'named'

It looks possible that you've somehow had the user 'named' deleted (and 
it formerly had id 511.) That would cause permission problems.

>
> I think the permissions stuff is unrelated to the port - it only 
> installs these files into /opt/local/var/named:
>
> % port contents bind9 | grep /opt/local/var/named
>   /opt/local/var/named/db.127.0.0.dist
>   /opt/local/var/named/db.cache.dist
>   /opt/local/var/named/db.localhost.dist
>
> 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.
>
> -- 
> Daniel J. Luke


-- 
Bill Cole
bill at scconsult.com or billcole at apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire