Project

General

Profile

Bug #5767

When first enabling DNS Resolver the test of the config fails

Added by Phillip Davis over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
DNS Resolver
Target version:
Start date:
01/13/2016
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.3
Affected Architecture:

Description

The current code in 2.3 tries to generate unbound.test.conf but with various references to "real" files in it like access_lists.conf and so on. If unbound is already up and running then those "real" files exist and the validation of unbound.test.conf passes. But if it is the very first time enabling unbound, then those files may not exist and the validation reports errors like in this forum post:
https://forum.pfsense.org/index.php?topic=105236.0

Associated revisions

Revision 1548bd35 (diff)
Added by Phillip Davis over 3 years ago

Fix #5767 config validation errors when first enabling DNS Resolver

Generate a complete set of test conf files in /var/unbound/test subdir when doing the validation of the tentative config that is being saved.
This avoids any dependency on any of the "real" files already existing in /var/unbound and also avoids the chance of overwriting a live file that is currently in use by the running unbound.
/var/unbound/test is removed once the validation has been done.
The real unbound conf files are created in /var/unbound like they always were after the user presses apply.

History

#2 Updated by Phillip Davis over 3 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#4 Updated by Steve Beaver over 3 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF