This was fixed yesterday upstream and is not yet released anywhere. For confidence in the change I'd prefer to wait for it to be released - not that they find issues in the fix.
The actual change is small and seems backportable even to trusty, but I had no time to check the context. Debian currently is ~2 months behind the last upstream release, given the cadence of upstream releases this will be released ~mid december. We can't really wait until March to pick it, but should wait for the upstream release. Until then we can try in a ppa if it actually is backportable and there Richard can check if the backport works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732150 Title: Unbound behaviour changes (wrong) when domain-insecure is set for a stub zone with multiple stub-addr(s) To manage notifications about this bug go to: https://bugs.launchpad.net/unbound/+bug/1732150/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
