Unbound frequent restarts

General
99

I've listed it earlier in this topic, but here it is again:

cat /var/cache/unbound/resolvconf_resolvers.conf
# Generated by resolvconf

forward-zone:
        name: "localdomain"
        forward-addr: the IP v6 address of my pihole - masked for privacy

forward-zone:
        name: "."
        forward-addr: the IP v6 address of my pihole - masked for privacy

I assume the forward-zone: name: "." is the result of my unbound config has an entry for auth-zone: name: "." (read here).

Not sure I understand this. Both my IPv6 and IPv4 addresses haven't changed for a few weeks. I know this because I have a cron script running that checks this every 30 minutes.
The IP only changes when my ISP either kicks my modem (forced config change - we're not allowed access to the modem) or kicks their own IPv6 infra (sometimes, but not always announced on their status page).

anyway, since I'm adding another post, I might just as well let you now I've commented out the line

#unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf

in /etc/resolvconf.conf, done yesterday evening 22h43, no unbound stop messages since than. This is no confirmation this will definitely work, will need to monitor this for at least 3 or 4 days.
Why did I decided to do this? My system also has knot-resolver installed. I use kresd as a resolver for some lists I build overnight and publish on GitHub. I don't want the dnsmasq and unbound cache to hold these entries, hence using another local recursive resolver for this purpose only. Nothing to do with pihole, but I noticed /etc/resolvconf.conf doesn't contain an entry for knot-resolver (kresd), and looking at the logs, kresd never restarts. I would expect kresd to respond to IP changes in the same way unbound does.

edit
just checked, my own audit method (script as suggested by DL6ER) is still running. ther was an entry:

Mon 31 May 00:30:15 CEST 2021,6007,/bin/sh /usr/sbin/resolvconf -a eth0.ra

which previously matched the exact same time of an unbound stop message. Not this time though, no unbound stop. This makes me hope, but again, monitoring this for a few days will confirm...
/edit