Wouter Wijngaards

Since the commandline start works fine, it is not an issue with the configuration or the software itself. That is working fine. Something is wrong when you start it with...

Hi, You seem to ask a question directed at other users. They can respond here, but we have a users mailing list for NSD and for Unbound, where people can...

Could you tell more what you are trying to do? You want some readonly data in the /usr system but a chroot as well? And for certain files, like the...

So, what pieces of data are you trying to have where? NSD would need access from its chroot to these pieces of data, so during the chroot, they need to...

Are the folders in the path accessible? Also to the username that nsd or unbound runs as? I mean the chmod of the directories, like /run/nsd.

You omitted the `ls -ld /run/nsd` , the permissions on that directory also have to allow NSD to access it. In reality this bug, if you installed the debian package,...

But, now I see that under the usename NSD you can ls the file owned by user nsd of nsd.pid. So it should work, but it does not. Perhaps the...

Yeah I do not see the problem either. There was a bunch of discussion about systemd files and after that we removed out contrib/nsd.service example for systemd configuration. Another thing...

So it works to create the pidfile, that does not have an error now. It only prints an error on exit, that you could ignore; removal of the old pidfile...

The minimal responses setting as it is implemented right now removes the NS record from the authority section and then those addresses from the additional section. The response you show...