Wouter Wijngaards

Yes, unbound uses the same commandline option `-c file` as on Linux, if you change the commandline that it is started with. It can also be changed with the registry...

There is a standards document about this problem. https://datatracker.ietf.org/doc/html/rfc8906 RFC 8906, "_A Common Operational Problem in DNS Servers: Failure to Communicate_". Realistically, the upstream server should respond, with an error,...

The stack trace looks like this is the #411 issue. There is nothing really, that should be fixed. There is a workaround that I committed and this stops the loop,...

There is an option called `rpz-log: yes`. If that is enabled the rpz actions are logged with the query that caused it. It then appears on a separate line, from...

There is `log-local-actions: yes` and this logs actions from local zones, for every local zone. But that would only print the local zone information and the action taken. Also on...

The strdup call is nicer with error handling. It is added in the commit above. The prints in the usage printout routine from unbound-control do not need such error handling,...

I think it is a good idea to avoid ignorance of return values. But for such print statements, in the usage output, I think that is not nicer to check...

Yes, it is important to check for data output failures. For that, checking the return value of print function when NSD is printing to file, in other places, is important....

Yes, that is true, that error handling fits in that way. That is interesting to read. :-) For the usage printout, I think the result of handling the errors would...

Unbound probably works fine on the linux distro you want, just fetch the source code and compile. The https://packages.ubuntu.com/source/noble/unbound link shows packages.