Wouter Wijngaards
Wouter Wijngaards
fatal error: could not open autotrust file for writing, /root.key.10018-0-16059b0: Permission denied
I believe that the list of `getpid()` calls could be that unbound is logging a number of messages. Each has the pid of unbound and the timestamp, and that call...
The setting `use-caps-for-id: yes` could be the issue, try `use-caps-for-id: no`. If there is fallback that needs a lot of additional queries, and this option is not common, so I...
I do not know a value calculation for them. Perhaps leave them at default. Or 64k for less buffer size but also less memory consumption, since the test involves opening...
Since I cannot reproduce this, it comes down to figuring out how to reproduce it or attempting to get more information. The error is in the libevent library. Is it...
After searching the code for the event for `comm_point_tcp_handle_callback`, I have found that it has a boolean, event_added, and this tracks if the event has been added, with event_add, or...
It seems this is not really about trust anchor update, but about priming the root key? Because that is what the error says. But the issue talks about trust anchor...
There have been fixes in the unbound 1.20.0 release, and recent releases, for RPZ processing, in particular in the iterator. So it seems likely that the update causes the RPZ...
The queries are called root priming queries [RFC8109]. This happens because unbound is asked to perform recursion, the iterative lookup of the DNS queries using authoritative servers. This is the...
Unbound does not make root priming queries, unless it needs to make them. The root priming happens when unbound performs recursion. In which case, what with following the delegations from...
It should not loop like that; I would like to know what unbound is looping over. The perf says this is entirely within libevent and some anonymous functions, I assume...