I think so. Although when the resolvconf
command is called by e.g. dhcpcd
, then usually because it does want to change something, but probably it is done as well when actually no related IP has changed. Not sure where to report bugs. GitHub is a mirror only with not a single issue. Here the official website of the project: openresolv
To list the possible solutions from least to most intrusive (still all to be verified!):
- Comment the
unbound_conf
setting (or set it with empty value:unbound_conf=
) in/etc/resolvconf.conf
, to make the special unbound script exit before doing something: openresolv/unbound.in at b51e465c3d289da7bee9843ddc2eb5404e72b954 · NetworkConfiguration/openresolv · GitHub - Set
unbound=off
in/etc/resolvconf.conf
, to make the special unbound script not being called in the first place: openresolv/resolvconf.in at b51e465c3d289da7bee9843ddc2eb5404e72b954 · NetworkConfiguration/openresolv · GitHub - Install the
resolvconf
package to replaceopenresolv
, which has no special unbound script, or any other script to configure anything else but/etc/resolv.conf
.