On Wed, 19 Jan 2022 16:33:46 +0100 Vincent Lefevre <vinc...@vinc17.net> wrote:
Package: unbound
Version: 1.13.1-1
Severity: important
Note: The changes I've done on /etc/resolvconf/update.d/unbound
is just logging messages (to known what's going on).
When /run/resolvconf/interface/NetworkManager is obsolete (which
can occur as NetworkManager is not the only was to connect: I use
it only for wifi), DNS resolution no longer works.
I fear that even when this file is not obsolete, unbound does not
work as expected.
Well, this file is *disabled*. We added a note to this file telling
just that, to clarify:
+#
+# This update hook is **disabled** by default: the execute bit is not set.
+#
+# This hook can be problematic, especially if the
+# upstream nameservers do not perform DNSSEC validation, or if a
+# "forward-zone" declaration for the root zone has been statically
+# configured by the administrator. In previous versions, the hook was
+# enabled by default, but it is now disabled by default. It can be
+# explicitly enabled by running "chmod +x /etc/resolvconf/update.d/unbound".
+#
+# If enabled (by setting the execute bit), upstream nameservers
+# supplied by resolvconf will be configured into the running Unbound instance
+# via the "unbound-control forward" command.
+#
But besides that, what exactly do *you* think is buggy about it?
Thanks,
/mjt
