Actions
Bug #13254
closedDNS resolver does not update its configuration or reload during link down events
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
23.01
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
How to reproduce:
1) Configure the interface with Static IPv4
2) Select this interface in the "Network Interfaces" and/or "Outgoing Network Interfaces" list on the Services / DNS Resolver page
3) Disconnect this interface
3) Check the interface/outgoing-interface entries in /var/unbound/unbound.conf
4) /var/unbound/unbound.conf contains a disconnected interface IP
5) If you restart the service, the unbound.config won't contain disconnected interface IP anymore.
It's related to https://redmine.pfsense.org/issues/12613
Related issues
Updated by Jim Pingle over 2 years ago
- Subject changed from DNS resolver doesn't update unbound.conf file during Link down events to DNS resolver does not update ``unbound.conf`` file during link down events
- Target version changed from 23.01 to 2.7.0
Updated by Jim Pingle over 2 years ago
- Related to Bug #12613: DNS Resolver does not restart during link up/down events on a static IP address interface added
Updated by Jim Pingle over 2 years ago
- Plus Target Version changed from 22.09 to 22.11
Updated by Jim Pingle almost 2 years ago
- Plus Target Version changed from 22.11 to 23.01
Updated by Jim Pingle almost 2 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 31c37082cad1ca068fc22d93fe3dc3c6a8005144.
Updated by Danilo Zrenjanin almost 2 years ago
- Status changed from Feedback to Resolved
Tested against:
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 almost 2 years ago
- Subject changed from DNS resolver does not update ``unbound.conf`` file during link down events to DNS resolver does not update its configuration or reload during link down events
Actions