20 Kvě
2020
20 Kvě
'20
16:49
Hi,
there are two possible approaches:
1. Reconfigure running instance using
https://knot-resolver.readthedocs.io/en/v5.1.1/daemon-scripting.html
This needs to be repeated for all running instances independenty.
2. Modify configuration file and use Zero-downtime trick
https://knot-resolver.readthedocs.io/en/v5.1.1/systemd-multiinst.html#zero-…
We are very much interested in knowing what you need to reconfigure and how often, please
participate in https://www.knot-resolver.cz/survey/ .
Petr Špaček @ CZ.NIC
On 20. 05. 20 16:34, Pierrick CHOVELON wrote:
Hi all,
Is there a way to reload dynamically the knot-resolver configuration without stopping
knot-resolver ?
e.g I have to add this in the config file
|extraTrees = policy.todnames({||'foo.example.net
<http://foo.example.net>'||})|
|policy.add(policy.suffix(policy.FLAGS({||'NO_CACHE'||}), extraTrees))|
|policy.add(policy.suffix(policy.FORWARD({||'192.168.0.15'||}), extraTrees))|
|
|||
Is there a sort of CLI command to take it in account ?
Regards
______________________________
*Pierrick CHOVELON I *Ingénieur système
**
*Advanced Software I IT
*
+33 4 77 43 27 05 /
/
pierrick.chovelon(a)savoye.com <mailto:pierrick.chovelon@savoye.com>
*SAVOYE - 8, rue de la Richelandière - 42100 - Saint-Etienne - France*
*/Savoye recrute ! <https://careers.savoye.com/#!/fr/index> - /*www.savoye.com
<http://www.savoye.com>