restart of unbound service when (unused) interface changes

[Mike Brust]

Hi all,

I am running unbound on a Debian system with two interfaces (eth0 and wlan0).
All communication goes with eth0

In The unbound.conf I have defined
„Interface: 127.0.0.1"

Unbound is working as designed, cache is being build up, all good.

However, when the wlan0 interface goes down/up accidentally, unbound restarts and cache is being reset.

How can I prevent a restart of the unbound?
Or let unbound ignore the secondary interface?
Update from 1.9.0 to 1.10.1 did not help

thanks

Syslog report:
2020-06-05
08:02:02
Information
raspberrypidns
daemon
unbound
[569:0] info: start of service (unbound 1.10.1).
2020-06-05
08:02:01
Notice
raspberrypidns
daemon
unbound
[569:0] notice: Restart of unbound 1.10.1.
2020-06-05
08:02:01
Information
raspberrypidns
daemon
unbound
[569:0] info: service stopped (unbound 1.10.1).
2020-06-05
08:01:34
Information
raspberrypidns
daemon
unbound
[569:0] info: start of service (unbound 1.10.1).
2020-06-05
08:01:33
Notice
raspberrypidns
daemon
unbound
[569:0] notice: Restart of unbound 1.10.1.
2020-06-05
08:01:33
Information
raspberrypidns
daemon
unbound
[569:0] info: service stopped (unbound 1.10.1).
2020-06-05
08:00:58
Information
raspberrypidns
daemon
unbound
[569:0] info: start of service (unbound 1.10.1).
2020-06-05
08:00:57
Notice
raspberrypidns
daemon
unbound
[569:0] notice: Restart of unbound 1.10.1.
2020-06-05
08:00:56
Information
raspberrypidns
daemon
unbound
[569:0] info: service stopped (unbound 1.10.1).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20200608/439621d1/attachment.htm>