I've reproduced this on a test system to which I have full access.
At the time DNS starts failing, /var/snap/maas/common/log/named.log shows:
25-Jul-2020 09:44:34.333 ../../../lib/dns/rbtdb.c:1499: fatal error:
25-Jul-2020 09:44:34.333 RUNTIME_CHECK(rbtdb->next_serial != 0) failed
25-Jul-2020 09:44:34.333 exiting (due to fatal error in library)
25-Jul-2020 09:44:38.443 starting BIND 9.11.3-1ubuntu1.12-Ubuntu (Extended Support Version) <id:a375815>
So BIND crashes and is restarted - with a bad configuration.
I think the crash is actually due to changing the dnssec-validation option and reloading, and restarting instead of reloading prevents this crash. This means I should use a different 'quick fix'!
However, I can't find anything in the logs as to why the configuration file was changed, which is the real issue here.
I've reproduced this on a test system to which I have full access.
At the time DNS starts failing, /var/snap/ maas/common/ log/named. log shows:
25-Jul-2020 09:44:34.333 ../../. ./lib/dns/ rbtdb.c: 1499: fatal error: CHECK(rbtdb- >next_serial != 0) failed 1ubuntu1. 12-Ubuntu (Extended Support Version) <id:a375815>
25-Jul-2020 09:44:34.333 RUNTIME_
25-Jul-2020 09:44:34.333 exiting (due to fatal error in library)
25-Jul-2020 09:44:38.443 starting BIND 9.11.3-
So BIND crashes and is restarted - with a bad configuration.
I think the crash is actually due to changing the dnssec-validation option and reloading, and restarting instead of reloading prevents this crash. This means I should use a different 'quick fix'!
However, I can't find anything in the logs as to why the configuration file was changed, which is the real issue here.