On 2018-08-04 22:27, Bjoern Franke wrote: Hi, thank you for supplying your configuration, I think we have it figured out now. There are some permissions/capabilities issues. To resolve them, please perform the following steps: 1. uncomment/add the line user: knot:knot to the server section of your configuration. 2. Change the storage of your zones and databases from /etc/knot/zones to a directory preferably outside of /etc/. The /var/lib/knot directory is ideal and is meant for this purpose, since it already has the knot:knot ownership set. If you choose a different directory, set its owner to knot:knot. 3. Make sure that the zone files are accessible for read and write by the user knot. The same should hold for any files in the storage directory, but if you simply remove timers, journal, etc., they will be generated again with the correct permission next time you run knotd. 4. Preferably, use systemd to run knotd on your server. Store your configuration file in /etc/knot/knot.conf which is the default path and use $ systemctl start knot $ systemctl stop knot $ systemctl status knot.service to start, stop or print information about running knotd. These steps will make sure that knotd will drop its root privileges after starting but can still access the files it needs (zone files, timers, ...) and you should be good to go! Let us know if you experience any difficulties. Kind Regards, Mark Karpilovskij