unbound forgets forwarder set via dhcp when config is reloaded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unbound (Ubuntu) |
Triaged
|
Undecided
|
Unassigned |
Bug Description
unbound is integrated quite nicely with resolvconf. When a system boots up and eth0 is configured via dhcp and gets a DHCP server, the forwarder is set properly. When you restart unbound, the forwarder is set properly as well.
But if you reload the config, the forwarder is forgotten since the resolvconf update script isn't called:
root@ip-
172.31.0.2
root@ip-
root@ip-
off (using root hints)
root@ip-
ok
root@ip-
172.31.0.2
root@ip-
root@ip-
172.31.0.2
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unbound 1.5.8-1ubuntu1
ProcVersionSign
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Mar 22 21:38:25 2017
Ec2AMI: ami-5aee2235
Ec2AMIManifest: (unknown)
Ec2Availability
Ec2InstanceType: t2.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: unbound
UpgradeStatus: No upgrade log present (probably fresh install)
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