It shut down because that's when you stopped it? Some other reason? The startupitem stuff in the Portfile was last changed 2020-12-31, so I don't think that's related to any problem with the latest bind9 port.
If you try and start named manually with a high debug level (and optionally with -g so it forces all logging to stderr) you may get some more insight on why it doesn't want to run for you now. > On May 28, 2025, at 4:28 AM, Mark Lucas via macports-users > <[email protected]> wrote: > > Looking at the log it seems the server shut down at around 3:58 this morning. > > ... > 28-May-2025 03:58:38.076 general: stopping statistics channel on > 127.0.0.1#5050 > 28-May-2025 03:58:38.076 general: stopping statistics channel on ::1#5050 > 28-May-2025 03:58:38.076 general: shutting down > 28-May-2025 03:58:38.109 general: exiting > > > The DNS operates as a slave for various zones and the log shows that some > failed to refresh because the master server VLAN IP for the zone was > unreachable. However this has been the case for some time and has not caused > problems in the past. I have commented out the zones in the config but it > still will not launch. > > The log shows no new entries since 3:58 this morning. > > Forgot to mention the OS is 15.5 > > Thanks > >> On 28 May 2025, at 08:49, Ryan Carsten Schmidt <[email protected]> >> wrote: >> >> On May 28, 2025, at 01:51, Mark Lucas wrote: >>> >>> >>> >>> latest version of bind9 (bind9 @9.20.9_0) will no longer launch. >> >> What happens instead? What error message do you get? -- Daniel J. Luke
