A good environment to test this is actually AWS where I noticed this :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675192
Title:
unbound forgets forwarder set via dhcp when config is reloaded
Thanks for triaging. I think you are right, restarts loose the
forwarders as well. At least most the time, I think I saw one instance
where it didn't happen but maybe the DHCP lease happened to be renewed
at the same time or I just imagined it.
--
You received this bug notification because you
I must be missing something obvious, as well.
When I run `service unbound restart` after specifying a forwarder with
`unbound-control` first, `unbound-control forward` reports 'off (using
root hints)' afterwards. This is in a VM using DHCP for its IP address.
Is there some additional configuration
Also, I note that in 17.04 (unlike 16.04), there is a unbound-
resolvconf.service which has:
[Unit]
Description=Unbound DNS server via resolvconf
After=unbound.service
PartOf=unbound.service
ConditionFileIsExecutable=/sbin/resolvconf
[Service]
RemainAfterExit=yes
ExecStart=/usr/lib/unbound/packag
Hello,
Thank you for filing this bug report!
This seems like an issue that comes from the Debian packaging of
unbound. Would you be willing to file a bug with them to see what they
think should be changed in /etc/init.d/unbound?
Thanks,
Nish
** Changed in: unbound (Ubuntu)
Status: New =>
