Control: reassign -1 unbound 1.13.1-1 Control: retitle -1 unbound: /etc/resolvconf/update.d/unbound should be reenabled by default
The unbound behavior should be similar to the one without resolvconf installed. So /etc/resolvconf/update.d/unbound should be reenabled by default so that name resolution works when UDP is filtered, and perhaps more generally to make it work with captive portals, which are common nowadays. The current situation is very confusing, and the installation of resolvconf (e.g. because some other package needs it) may make things no longer work as expected. On 2022-01-05 16:22:16 +0100, Vincent Lefevre wrote: > Indeed, this was the cause of the issue. After making unbound > executable, I now get: > > # unbound-control forward > 192.168.43.173 192.168.1.1 > > instead of "off". > > However, this is broken: 192.168.1.1 shouldn't be there!!! Concerning this issue, this is because a reboot was needed, as documented in the resolvconf(8) man page (I think that resolvconf should have been smarter, but this is probably not a big issue). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
