Unbound is restarting every 30 minutes

Networking
1

Today I noticed that unbound has been restarting every 30 minutes since the end of September, which was definitely not the case before.
Is this normal now?

19:30:00 unbound: [27958:0] info: generate keytag query _ta-4a5c-4f66. NULL IN
19:29:50 unbound: [27958:0] info: start of service (unbound 1.18.0).
19:29:50 unbound: [27958:0] notice: init module 1: iterator
19:29:50 unbound: [27958:0] notice: init module 0: validator
19:29:49 unbound: [27958:0] notice: Restart of unbound 1.18.0.
19:29:48 unbound: [27958:0] info: 0.524288 1.000000 1
19:29:48 unbound: [27958:0] info: 0.262144 0.524288 13
19:29:48 unbound: [27958:0] info: 0.131072 0.262144 33
19:29:48 unbound: [27958:0] info: 0.065536 0.131072 20
19:29:48 unbound: [27958:0] info: 0.032768 0.065536 5
19:29:48 unbound: [27958:0] info: 0.016384 0.032768 3
19:29:48 unbound: [27958:0] info: 0.000000 0.000001 5
19:29:48 unbound: [27958:0] info: lower(secs) upper(secs) recursions
19:29:48 unbound: [27958:0] info: [25%]=0.0884736 median[50%]=0.158875 [75%]=0.238313
19:29:48 unbound: [27958:0] info: histogram of recursion processing times
19:29:48 unbound: [27958:0] info: average recursion processing time 0.160369 sec
19:29:48 unbound: [27958:0] info: server stats for thread 0: requestlist max 2 avg 0.117647 exceeded 0 jost led 0
19:29:48 unbound: [27958:0] info: server stats for thread 0: 146 queries, 66 answers from cache, 80 recursi ons, 5 prefetch, 0 rejected by ip ratelimiting
19:29:48 unbound: [27958:0] info: service stopped (unbound 1.18.0).
19:03:03 unbound: [27958:0] info: generate keytag query _ta-4a5c-4f66. NULL IN
18:59:49 unbound: [27958:0] info: generate keytag query _ta-4a5c-4f66. NULL IN
18:59:49 unbound: [27958:0] info: start of service (unbound 1.18.0).
18:59:49 unbound: [27958:0] notice: init module 1: iterator
18:59:49 unbound: [27958:0] notice: init module 0: validator
18:59:47 unbound: [27958:0] notice: Restart of unbound 1.18.0.
18:59:47 unbound: [27958:0] info: 0.262144 0.524288 4
18:59:47 unbound: [27958:0] info: 0.131072 0.262144 20
18:59:47 unbound: [27958:0] info: 0.065536 0.131072 13
18:59:47 unbound: [27958:0] info: 0.032768 0.065536 3
18:59:47 unbound: [27958:0] info: 0.016384 0.032768 2
18:59:47 unbound: [27958:0] info: 0.000000 0.000001 1
18:59:47 unbound: [27958:0] info: lower(secs) upper(secs) recursions
18:59:47 unbound: [27958:0] info: [25%]=0.0894818 median[50%]=0.147456 [75%]=0.217907
18:59:47 unbound: [27958:0] info: histogram of recursion processing times
18:59:47 unbound: [27958:0] info: average recursion processing time 0.154353 sec
18:59:47 unbound: [27958:0] info: server stats for thread 0: requestlist max 1 avg 0.037037 exceeded 0 jost led 0
18:59:47 unbound: [27958:0] info: server stats for thread 0: 104 queries, 61 answers from cache, 43 recursi ons, 11 prefetch, 0 rejected by ip ratelimiting
18:59:47 unbound: [27958:0] info: service stopped (unbound 1.18.0).
2
3

Ok thanks, so there is no solution yet ?
Does this mean I have any disadvantages that other things don’t work as they should?

4

I see the same messages unbound restart messages in the messages log.

I am curious, are there any issues you see when these unbound restarts happen (beside the restart message)?