Regression: Upon booting in range of a "connect automatically" WLAN, unbound is unable to resolve, with several of these in the log:
Mar 24 14:30:26 vimes unbound[1262]: [1262:0] error: .: failed lookup, cannot probe to master k.root-servers.net
Mar 24 14:30:26 vimes unbound[1262]: [1262:0] error: .: failed lookup, cannot probe to master g.root-servers.net
"sudo unbound-control reload" is required to make name resolution work again.
I'm using "dns=unbound" in /etc/NetworkManager/NetworkManager.conf.
distro-sync back to release version fixes this.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
To be clear about my situation: dnssec-trigger with unbound 1.7.0 fails to resolve any names when using the shipped 1.7.0 configuration which contains auth-zone: config for the root zone. This is directly after a reboot.
After commenting out the auth-zone: config, it works again, even after a reboot.
This update has been submitted for testing by pwouters.
This update has been pushed to testing.
no regressions noted
Regression: Upon booting in range of a "connect automatically" WLAN, unbound is unable to resolve, with several of these in the log: Mar 24 14:30:26 vimes unbound[1262]: [1262:0] error: .: failed lookup, cannot probe to master k.root-servers.net Mar 24 14:30:26 vimes unbound[1262]: [1262:0] error: .: failed lookup, cannot probe to master g.root-servers.net
"sudo unbound-control reload" is required to make name resolution work again.
I'm using "dns=unbound" in /etc/NetworkManager/NetworkManager.conf.
distro-sync back to release version fixes this.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
works for me
Opened rhbz #1560223 to track network reconnect issue above.
All name resolution fails for me
Works
Working.
To be clear about my situation: dnssec-trigger with unbound 1.7.0 fails to resolve any names when using the shipped 1.7.0 configuration which contains auth-zone: config for the root zone. This is directly after a reboot.
After commenting out the auth-zone: config, it works again, even after a reboot.
Breaks internet connection for me after some usage, probably also rhbz #1560223.
This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes
Works for me.
Repeatedly crashes with a buffer overflow:
Apr 01 09:46:56 arden.compton.nu unbound[15415]: [15415:0] notice: sendto failed: Invalid argument Apr 01 09:46:56 arden.compton.nu unbound[15415]: [15415:0] notice: remote address is (inet_ntop error) port 45798 Apr 01 09:46:56 arden.compton.nu unbound[15415]: *** buffer overflow detected ***: /usr/sbin/unbound terminated Apr 01 09:46:56 arden.compton.nu unbound[15415]: [15415:0] notice: sendto failed: Invalid argument Apr 01 09:46:56 arden.compton.nu unbound[15415]: [15415:0] notice: remote address is (inet_ntop error) port 45798 Apr 01 09:46:56 arden.compton.nu unbound[15415]: [15415:0] notice: sendto failed: Invalid argument Apr 01 09:46:56 arden.compton.nu unbound[15415]: [15415:0] notice: remote address is (inet_ntop error) port 45798 Apr 01 09:46:56 arden.compton.nu unbound[15415]: [15415:0] notice: sendto failed: Invalid argument Apr 01 09:46:56 arden.compton.nu unbound[15415]: [15415:0] notice: remote address is (inet_ntop error) port 45798 Apr 01 09:46:56 arden.compton.nu unbound[15415]: [15415:0] notice: sendto failed: Invalid argument Apr 01 09:46:56 arden.compton.nu unbound[15415]: [15415:0] notice: remote address is (inet_ntop error) port 45798 Apr 01 09:46:56 arden.compton.nu systemd[1]: unbound.service: Main process exited, code=killed, status=6/ABRT Apr 01 09:46:56 arden.compton.nu systemd[1]: unbound.service: Unit entered failed state. Apr 01 09:46:56 arden.compton.nu systemd[1]: unbound.service: Failed with result 'signal'.
works for me
This update has been obsoleted by unbound-1.7.0-4.fc27.