opnsense
os-bind: Add the ability to add custom directives to configuration (`named.conf`)
Important notices Before you add a new report, we ask you kindly to acknowledge the following:
- [X] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
- [X] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
- [X] When the request is meant for an existing plugin, I've added its name to the title.
Is your feature request related to a problem? Please describe.
There is no way to add custom directives to the configuration (named.conf). There are many edge cases in BIND, and it's prohibitive to support all of them in the GUI. However, if you need to add custom directives, you have to edit the named.conf file directly, and those changes are lost as soon as you edit the configuration through the GUI.
Describe the solution you'd like An option in the General tab (in "Advanced Mode") that allows you to add custom directives to the configuration file.
Describe alternatives you've considered
An alternative would be to create a blank named.local.conf file, and always include it using the include directive, which would allow end users to manually modify the named.local.conf file and have those directives added to the main config file.
I'm not against including named.local.conf but custom options is prohibited.
Why are custom options prohibited? We do this same thing for HAProxy and a few other plugins.