add validation of Unbound advanced configuration
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 over 6 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.