Hi,
I’d like to proporse an update to knot-resolver package to support custom configuration tweaks.
Since the running configuration file for kresd daemon is generated by /etc/init.d/kresd, it is hard to inject any configuration parameters (in my case a policy for my non-public domain and a hints file) without modification of the /etc/init.d/kresd itself (my fix is to cat my_config_file >>$CONFIGFILE in init_header() function of the script.
This of course works, but in an event of package update, it will be lost and has to be re-hacked.
My proporsal is to add an option into /etc/config/resolver in ‘kresd’ section (something like option include ‘path_to_file’).
Peter