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

2022-09-22 Thread Mark Lucas
Having fixed the ownership and managed to manually startup named, the temp log produced cryptically ended by saying; 22-Sep-2022 16:44:15.726 general: critical: loading configuration: file not found 22-Sep-2022 16:44:15.727 general: critical: exiting (due to fatal error) Turns out that for some

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

2022-09-22 Thread Bill Cole
On 2022-09-22 at 10:55:06 UTC-0400 (Thu, 22 Sep 2022 15:55:06 +0100) Mark Lucas is rumored to have said: Sorry to probably ask the obvious but what command do I use to start it manually? /opt/local/sbin/named -g -u named That will start named in the foreground of your terminal and force all

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

2022-09-22 Thread Bill Cole
On 2022-09-22 at 10:27:16 UTC-0400 (Thu, 22 Sep 2022 10:27:16 -0400) Daniel J. Luke is rumored to have said: On Sep 22, 2022, at 8:56 AM, Mark Lucas 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

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

2022-09-22 Thread Mark Lucas
Sorry to probably ask the obvious but what command do I use to start it manually? > On 22 Sep 2022, at 15:27, Daniel J. Luke wrote: > >> On Sep 22, 2022, at 8:56 AM, Mark Lucas wrote: >> I just updated to bind 9.18.7 (Intel mac mini - macOS 12.6 ) and despite >> checking the config was ok,

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

2022-09-22 Thread Daniel J. Luke
> On Sep 22, 2022, at 8:56 AM, Mark Lucas 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

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

2022-09-21 Thread Daniel J. Luke
On Aug 31, 2021, at 8:52 AM, FritzS GMX wrote: >>> But the named daemon don't run. >>> >>> All this commands don’t work: >>> >>> sudo launchctl load -wF /Library/LaunchDaemons/org.macports.bind9.plist >>> >>> sudo /opt/local/bin/port load bind9 >>> >>> sudo /opt/local/sbin/rndc reload >>>

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

2021-08-31 Thread FritzS GMX
> Am 31.08.2021 um 11:51 schrieb Ryan Schmidt : > > On Aug 25, 2021, at 02:00, FritzS GMX wrote: > >> after migration from my profile & apps from ElCapitan to Big Sur I >> reinstalled all the MacPorts programs, >> bind9 are new compiled on my MacMini M1 too. >> >> But the named daemon don't

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

2021-08-31 Thread Ryan Schmidt
On Aug 25, 2021, at 02:00, FritzS GMX wrote: > after migration from my profile & apps from ElCapitan to Big Sur I > reinstalled all the MacPorts programs, > bind9 are new compiled on my MacMini M1 too. > > But the named daemon don't run. > > All this commands don’t work: > > sudo launchctl

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

2021-08-25 Thread FritzS GMX
after migration from my profile & apps from ElCapitan to Big Sur I reinstalled all the MacPorts programs, bind9 are new compiled on my MacMini M1 too. But the named daemon don't run. All this commands don’t work: sudo launchctl load -wF /Library/LaunchDaemons/org.macports.bind9.plist sudo