For BIND 9.20.7 and 9.21.6 we changed the service type from "forking" to "notify", also ExecStart now has the "-f" option:

-[Service]
-Type=forking
-ExecStart=/opt/isc/isc-bind/root/usr/sbin/named -u named
+[Service]
+Type=notify
+ExecStart=/opt/isc/isc-bind/root/usr/sbin/named -u named -f

Could you please give us the output of "systemctl status isc-bind-named.service" a few seconds after the service started? I'd be surprised to find it in the "Active: active (running)" state.

I failed to reproduce your problem on a clean Rocky Linux 8.10.

Michal

On 21/03/2025 20:43, Langlois Joël via bind-users wrote:
Hi everyone,

      After updating my isc-bind packages from 9.20.6-1.2 to 9.20.7-1.2, i try to start the service but it always « shutdown » by himself. My server is a Rocky Linux 8.10 and with the old version (9.20.6)  everything is working fine since many mounths. Here is a the part of the output log (with debug enable) where i saw the service going down (see netmgr ans shutting down below)! Any idea someone?

Thanks in advance

.

.

.

fetch: ultradns.info/NS

fetch: ultradns.co.uk/NS

fetch: ultradns.co.uk/NS

fetch: rds.ca/A

fetch: rds.ca/A

zone_maintenance: managed-keys-zone: enter

zone_dump: managed-keys-zone: enter

zone__settimer: managed-keys-zone: enter

dump_done: managed-keys-zone: enter

zone_journal_compact: managed-keys-zone: target journal size 0

journal file managed-keys.bind.jnw does not exist, creating it

fetch: rds.ca/A

fetch: rds.ca/A

fetch: rds.ca/A

fetch: rds.ca/A

netmgr 0x7fa151a7b1e0: Shutting down network manager

netmgr 0x7fa151a7b1e0: Shutting down network manager worker on loop 0x7fa151a39000(0)

no longer listening on 127.0.0.1#53

no longer listening on X.X.X.60#53

stopping command channel on 127.0.0.1#953

loop exclusive mode: starting

loop exclusive mode: started

shutting down

managed-keys-zone: final reference detached

.

.

================================

# systemctl status isc-bind-named.service

● isc-bind-named.service

   Loaded: loaded (/usr/lib/systemd/system/isc-bind-named.service; enabled; vendor preset: disabled)

   Active: failed (Result: timeout) since Fri 2025-03-21 14:47:08 EDT; 51min ago

  Process: 1531 ExecStart=/opt/isc/isc-bind/root/usr/sbin/named -u named -f $OPTIONS (code=exited, status=0/SUCCESS)

Main PID: 1531 (code=exited, status=0/SUCCESS)

Mar 21 14:45:37 dns_server named[1531]: checkhints: b.root-servers.net/ AAAA (2801:1b8:10::b) missing from hints

Mar 21 14:45:37  dns_server  named[1531]: checkhints: b.root- servers.net/AAAA (2001:500:200::b) extra record in hints

Mar 21 14:47:07 dns_server  systemd[1]: isc-bind-named.service: start operation timed out. Terminating.

Mar 21 14:47:07 dns_server  named[1531]: no longer listening on 127.0.0.1#53

Mar 21 14:47:07 dns_server  named[1531]: no longer listening on X.X.X.60#53

Mar 21 14:47:07 dns_server  named[1531]: stopping command channel on 127.0.0.1#953

Mar 21 14:47:07 dns_server  named[1531]: shutting down

Mar 21 14:47:08 dns_server   named[1531]: exiting

Mar 21 14:47:08 dns_server   systemd[1]: isc-bind-named.service: Failed with result 'timeout'.

Mar 21 14:47:08 dns_server  systemd[1]: Failed to start isc-bind- named.service.

#

------

Joe



--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to