Feature #4411
closedadd validation of Unbound advanced configuration
100%
Description
Something similar to dnsmasq's advanced config validation would be helpful for Unbound, to prevent users from creating configs with invalid syntax.
Updated by Paul K almost 10 years ago
One thing you might consider is adding 'server:' as the last keyword in all configuration files that are included in the main config file. That would effectively "break out" from whatever directive was last used in the included file. This way you wouldn't have to add 'server: in the advanced options and might prevent other issues down the road.
Updated by Chris Buechler over 9 years ago
- Target version set to 2.3
Pull request submitted:
https://github.com/pfsense/pfsense/pull/1779
Updated by Matthew Smith about 9 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 932711c7ec2a6cdd19a4a71b9812b1811dae348e.
Updated by Phillip Davis about 9 years ago
See https://github.com/pfsense/pfsense/pull/2048 for some fixups.
Updated by Matthew Smith about 9 years ago
Thanks for your corrections. It looks like they were merged this morning.