Hi Andrej at al, I'm reaching out to you on behalf of the CTTE. We have a dispute on the behavior of unbound when resolvconf is installed. The submitter argues that resolvconf should not be turning unbound into a forwarding resolver as its description indicates it to be recursive.
How do you see this? The resolvconf package description indicates that caches and resolver libraries should be affected. While unbound can cache, it also is a recursive resolver. Would you expect unbound to become a forwarding resolver upon installing resolvconf? We also observe that there are two distinct functions both implemented by resolvconf. One is to manage /etc/resolv.conf to point it at a local recursive resolver (e.g. bind, dnsmasq, unbound, ...) or externally provided servers (e.g. /etc/network/interfaces or DHCP). The other function is to reconfigure a local resolver to become a forwarding resolver for the externally provided servers. Plausibly, both functions could be viewed separately, but resolvconf combines them. Is that intentional? The package description of resolvconf does not clearly answer this. We suggest updating it. If the forwarding behavior is intended, it would be good if the description included that term. Thanks for your answers Helmut
