Public bug reported:
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-20-36:~# unbound-control forward
172.31.0.2
root@ip-172-31-20-36:~# service unbound reload
root@ip-172-31-20-36:~# unbound-control forward
off (using root hints)
root@ip-172-31-20-36:~# unbound-control forward 172.31.0.2
ok
root@ip-172-31-20-36:~# unbound-control forward
172.31.0.2
root@ip-172-31-20-36:~# service unbound restart
root@ip-172-31-20-36:~# unbound-control forward
172.31.0.2
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unbound 1.5.8-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
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)
Ec2AvailabilityZone: eu-central-1b
Ec2InstanceType: t2.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: unbound
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: unbound (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug ec2-images xenial
--
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1675192/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
