Wouter Wijngaards

When I try to replicate this, and I set `reuseport: yes` this succeeds just fine. This defines SO_REUSEPORT on the interface, which is faster. But it also permits several programs...

With a bit more testing, for this to work you have to enable the reuseport option for both servers. And that means also for the systemd-resolvd service, perhaps it already...

What do you want? Because, I thought it would be SO_REUSEPORT, but it is not. NSD attempts to open the 0.0.0.0 interface and this fails. This is what it does...

Okay, so I would like that too. I cannot really change the actual default so much because of backwards compatibility, but I am looking at what option you would need...

I am not sure if this helps you, but this script prints a nice list of interface: xx lines for me. `ip -o address | sed -e 's/^.*inet //' -e...

Not sure what that behaviour really is. I think it may do the same as that shell script but as an option, hence my oneliner and reference to the pullrequest...

Yes gearnode, you are right, but if I do that, and NSD skips binding the 0.0.0.0 interface, it would not be bound to any interface at all, and not answer...

You need to pass the configure option `./configure --with-ssl=/packages/openssl-1.1.1k-1/.self/develop` This is because the configure script then appends include and lib for those parts it needs. pkg-config is not something that...

When looking up the addresses for nameservers, unbound encounters too many NXDOMAIN responses for those lookup and stops to avoid causing a denial of service. The domain has a long...

Right now it counts the failure to lookup the nameservers as a failure that counts to the maximum failed nameserver lookups. Since the lookups are failing, it is reasonable that...