Bug #12612
closedDNS Resolver is restarted during every ``rc.newwanip`` event even for interfaces not used in the resolver
100%
Updated by Viktor Gurov about 3 years ago
Updated by Jim Pingle about 3 years ago
- Status changed from New to Pull Request Review
- Assignee set to Viktor Gurov
- Target version set to CE-Next
- Plus Target Version set to 22.05
Updated by Viktor Gurov almost 3 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
Applied in changeset 6ac625e8af602df3e70f41f17bd60631cd50e86a.
Updated by Jim Pingle almost 3 years ago
- Target version changed from CE-Next to 2.7.0
Updated by Jim Pingle over 2 years ago
- Subject changed from DNS Resolver is restarted at every rc.newwanip event to DNS Resolver is restarted during every ``rc.newwanip`` event
Updating subject for release notes.
Updated by Danilo Zrenjanin over 2 years ago
Tested
2.7.0-DEVELOPMENT (amd64) built on Wed Jun 01 06:12:27 UTC 2022 FreeBSD 12.3-STABLE
DNS resolver still restarts after every "rc.newwanip" no matter whether the interface is selected in the configuration of the DNS Resolver (in/out interface).
I selected only the LAN interface as DNS Resolver (in/out interface).
# Interface IP(s) to bind to interface: 192.168.20.1 # Outgoing interfaces to be used outgoing-interface: 192.168.20.1
After, rc.newwanip event on the WAN:
Jun 3 08:52:40 check_reload_status 399 rc.newwanip starting vtnet0
Unbound rebooted.
Jun 3 08:52:40 unbound 30541 [30541:0] info: service stopped (unbound 1.15.0). Jun 3 08:52:40 unbound 30541 [30541:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Jun 3 08:52:40 unbound 30541 [30541:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0 Jun 3 08:52:41 unbound 91463 [91463:0] notice: init module 0: validator Jun 3 08:52:41 unbound 91463 [91463:0] notice: init module 1: iterator Jun 3 08:52:41 unbound 91463 [91463:0] info: start of service (unbound 1.15.0).
Please check.
Updated by Jim Pingle over 2 years ago
- Status changed from Feedback to New
- Assignee deleted (
Viktor Gurov) - Plus Target Version changed from 22.05 to 22.09
The code looks like it should be right but we can debug it for the next release, it's not a blocker for 22.05.
Updated by Jim Pingle over 2 years ago
- Plus Target Version changed from 22.09 to 22.11
Updated by Jim Pingle about 2 years ago
- Plus Target Version changed from 22.11 to 23.01
Updated by Jim Pingle about 2 years ago
- Status changed from New to Feedback
Applied in changeset 1688a9608cbe5889f160dc4b4d3bcfc64fc856c4.
Updated by Danilo Zrenjanin about 2 years ago
- Status changed from Feedback to Resolved
Tested against the:
23.01-DEVELOPMENT (amd64) built on Thu Dec 01 06:04:55 UTC 2022 FreeBSD 14.0-CURRENT
It works as expected. I am marking this ticket resolved.
Updated by Jim Pingle about 2 years ago
- Subject changed from DNS Resolver is restarted during every ``rc.newwanip`` event to DNS Resolver is restarted during every ``rc.newwanip`` event even for interfaces not used in the resolver
Updating subject for release notes.
Updated by Jim Pingle over 1 year ago
- Subject changed from DNS Resolver is restarted during every ``rc.newwanip`` event even for interfaces not used in the resolver to DNS Resolver is restarted during every ``rc.newwanip`` event even for interfaces not used in the resolver
Updated by odo maitre over 1 year ago
It seems the problem is back in 2.7.0 - even if nothing has changed running rc.newwanip is restarting unbound.