Enable automatic restart on crashes

named contains high number of assertions checking expected state of the
daemon. That is part of defensive code style to prevent many attacks.
The most common failure is failing some assertion check in rare
circumstances. Even when this should not happen, try keeping the service
running. If such failed assertion produces coredump just from time to
time, avoid failing hard the whole service. coredumpctl will keep track
of all crashes anyway.

bind.spec

@@ -959,6 +959,7 @@ fi;
 %changelog
 * Fri Sep 30 2022 Petr Menšík <pemensik@redhat.com> - 32:9.18.7-3
 - Update License to SPDX identifier
+- Enable automatic restart on crashes
 
 * Sat Sep 24 2022 Petr Menšík <pemensik@redhat.com> - 32:9.18.7-2
 - Build ARM documentation also with older sphinx on RHEL9

named-chroot.service

@@ -25,6 +25,7 @@ ExecReload=/bin/sh -c 'if /usr/sbin/rndc null > /dev/null 2>&1; then /usr/sbin/r
 ExecStop=/bin/sh -c '/usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID'
 
 PrivateTmp=false
+Restart=on-abnormal
 
 [Install]
 WantedBy=multi-user.target

named.service

@@ -20,6 +20,7 @@ ExecReload=/bin/sh -c 'if /usr/sbin/rndc null > /dev/null 2>&1; then /usr/sbin/r
 ExecStop=/bin/sh -c '/usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID'
 
 PrivateTmp=true
+Restart=on-abnormal
 
 [Install]
 WantedBy=multi-user.target