Wouter Wijngaards

If you are eager to use, the branch is somewhat in a working state. At certain commits it works, passes tests, and reloads a growing list of configuration options.

A quick check with valgrind, shows that unbound has no memory leaks after a couple kill -HUP on it. I can see that the rss increases as well, with some...

For THP, transparent huge pages in madvise, I do not easily see how it could help since Unbound does not really have unused mapped memory sitting around. I also think...

From looking at the logs, it seems that the issue is that Unbound is configured to DNSSEC validate. The .eu DNSKEY is too large to fit in a UDP response....

Supposedly when Unbound makes a TCP connection, this is very similar to performing a `dig +tcp @that_ip_address query_name`. From the same host as where unbound is running. If the option...

If it works like that then why can Unbound not do it? It is really doing the same thing; unless you use configuration options like outgoing-interface, or socket options, or...

Perhaps the dig that was tried did not attempt to fetch the large response, the .eu DNSKEY query. And that is why it succeeded, instead of failed. I guess it...

We do not actually make the packages that are found in package repositories, like the one you are using. Those are created by the package maintainers from the software distributions,...

Perhaps enable the options: `verbosity: 5` and `logfile: "/root/unbound.log"` and `log-servfail: yes`. This enables lots more debug output, stores it in a file instead of spamming syslog, if you like,...

The logs contain a lot of 'network not reachable' and similar errors. So, it simply cannot send to the network. Not sure what it does then, perhaps that is why...