In the unbound-control command, the possibility to change the configuration in memory without clearing the cache is possible via the “set_option” argument.
The documentation tells that not all options can be used.
Can you list what is possible and what is not possible?
I have tried to change the “verbosity” but it do not work; the value returned with “unbound-control get_option: verbosity” gives however the new value.
The get_option values are most informative. There is a separate command
to change verbosity. Many of the yes/no options may be supported with
set_option. I would recommend editing the config file; as the results
of set_option are temporary, the config_file is reread on reload or restart.
Your experience with the verbosity is because the set_option and
get_option commands expose the internal code in unbound: the config
structure, which is sometimes used directly, and sometimes settings are
copied elsewhere (processed) at startup time.