Project

General

Profile

Actions

Bug #12613

closed

DNS Resolver does not restart during link up/down events on a static IP address interface

Added by Viktor Gurov about 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
DNS Resolver
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
22.05
Release Notes:
Default
Affected Version:
2.5.2
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 and reboot
3) Check the interface/outgoing-interface entries in /var/unbound/unbound.conf
3) Connect this interface - you'll see the "/rc.linkup: Hotplug event detected for INTERFACE static IP (x.x.x.x)" in logs
4) interface/outgoing-interface entries in /var/unbound/unbound.conf do not have a connected interface IP
5) Same with disconnecting - /var/unbound/unbound.conf still have a disconnected interface IP

Workaround - reboot or restart DNS Resolver

#11547 should be improved


Related issues

Related to Regression #12215: OpenVPN does not resync when running on a gateway groupClosed

Actions
Related to Regression #11570: Gateway monitoring services is not always restarted on interface events, which may prevent a WAN from recovering back to an online stateClosed

Actions
Related to Bug #13254: DNS resolver does not update its configuration or reload during link down eventsResolvedJim Pingle

Actions
Actions #1

Updated by Viktor Gurov about 2 years ago

  • Related to Regression #12215: OpenVPN does not resync when running on a gateway group added
Actions #2

Updated by Viktor Gurov about 2 years ago

  • Related to Regression #11570: Gateway monitoring services is not always restarted on interface events, which may prevent a WAN from recovering back to an online state added
Actions #3

Updated by Viktor Gurov about 2 years ago

  • Status changed from New to Feedback
  • Assignee set to Viktor Gurov
  • Target version set to CE-Next
  • Plus Target Version set to 22.05

should be fixed in #11570

Actions #4

Updated by Jim Pingle about 2 years ago

  • Target version changed from CE-Next to 2.7.0
Actions #5

Updated by Jim Pingle almost 2 years ago

  • Subject changed from unbound does not restarts on up/down link events on a static IP interface to DNS Resolver does not restart during link up/down events on a static IP address interface

Updating subject for release notes.

Actions #6

Updated by Danilo Zrenjanin over 1 year ago

Tested

2.7.0-DEVELOPMENT (amd64)
built on Wed Jun 01 06:12:27 UTC 2022
FreeBSD 12.3-STABLE

When I unplug the cable it doesn't update the unbound.conf accordingly. /var/unbound/unbound.conf still has the disconnected interface IP.

After reboot the /var/unbound/unbound.conf was updated accordingly.

It works fine when plugging the cable back. It automatically adds Interface IP to bind to and Outgoing interfaces to be used in the unbound.conf file.

Needs more testing.

Actions #7

Updated by Jim Pingle over 1 year ago

  • Status changed from Feedback to Resolved

Based on the original problem description and steps to reproduce it sounds like this specific request is fixed. For the other part, let's move that to a new Redmine issue and take care of it on a future release.

Actions #8

Updated by Jim Pingle over 1 year ago

  • Related to Bug #13254: DNS resolver does not update its configuration or reload during link down events added
Actions

Also available in: Atom PDF