Well, then I would suggest that you start by removing it from confd.conf to avoid confusion, since whatever you set there will always be ignored when you use confd_dyncfg.
There’s nothing “magic” with confd_dyncfg_init.xml, it is just like any other “CDB init file” - to quote the User Guide section “Loading initial data into CDB”:
At startup, when CDB is empty, i.e. no database files are found in
the CDB directory, CDB will try to initialize the database from all
instantiated XML documents found in the CDB directory.
I.e. once CDB has been created, changes to the init files, including confd_dyncfg_init.xml, has no effect. The whole point with confd_dyncfg is that you can change the ConfD daemon configuration by changing the actual contents of CDB, instead of editing a config file and reloading it. If you don’t intend to use this possibility, it is better to not use confd_dyncfg at all, since then the result is just that you have two config files to manage and edit instead of one.
If you do intend to make use of the confd_dyncfg functionality, but wish to have changes to the init file (i.e. new “initial values”) take effect without having to remove CDB and restart ConfD, you can (just as with any other CDB init file) explicitly load the updated file into CDB with
maapi_load_config() or the