Project

General

Profile

Actions
Copy link

Bug #11777

open

Input validation prevents DNS Resolver from being disabled

Added by Martin Thygesen about 3 years ago. Updated over 1 year ago.

Status:
New
Priority:
Very Low
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
04/03/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.5.0
Affected Architecture:
All

Description

When trying to disable unbound, the following error prevents the service from being turned off.

-----------------
The following input errors were detected:

The generated config file cannot be parsed by unbound. Please correct the following errors:
    [1617488979] unbound-checkconf[18250:0] fatal error: outgoing-interface: fe80::20c:29ff:fec7:63f1%em0 present twice, cannot bind same ports twice.
-----------------

taxonomy
user was operating with unbound dns resolver normally
system was setup for network interfaces LAN & DMZ & LOOPBACK (v4 & v6)
system was setup for outbound network interfaces WAN (v4 & v6)
user installed bind package to replace unbound but did not activate it.
user tried to disable unbound and was presented with this error message.
user stopped the unbound service from the dashboard and retried to disable the configuration, outcome failed

Workaround:
user adjusted the network interfaces to loopback
user adjusted the outbound network interface setting to loopback
user saved the config
user disabled unbound, and was successful in disabling the service.

Recommendation:
remove some of the check conditions that prevent the service config from being disabled
the service can clearly be stopped without the configuration process being impacted.
the parse of the configuration is too restrictive in this case.

Actions
Copy link

Also available in: Atom PDF