Dear Folks,
This question is about the version numbering system of unbound.
Does the change from 1.6.x to 1.7.x indicate a major change of the
software, or is it an incremental change in the way that 1.6.8 was an
incremental change from 1.6.7?
We are running 1.6.8 in production. Should we
On 24/07/17 12:57 +0200, W.C.A. Wijngaards via Unbound-users wrote:
On 21/07/17 05:29, Nick Urbanik via Unbound-users wrote:
On 06/07/17 18:13 +1000, Nick Urbanik via Unbound-users wrote:
A DNS server running unbound 1.6.3 has these messages; any suggestions
on what is happening?
error
Dear Folks,
On 06/07/17 18:13 +1000, Nick Urbanik via Unbound-users wrote:
A DNS server running unbound 1.6.3 has these messages; any suggestions
on what is happening?
error: serviced_tcp_initiate: failed to send tcp query
error: outgoing tcp: bind: Address already in use
Could our setting
Dear Folks,
A DNS server running unbound 1.6.3 has these messages; any suggestions
on what is happening?
error: serviced_tcp_initiate: failed to send tcp query
error: outgoing tcp: bind: Address already in use
--
Nick Urbanik http://nicku.org 808-71011 nick.urba...@optusnet.com.au
GPG: 7FFA
Dear Folks,
I'm trying to understand the exact meaning of this part of the
description of ratelimit in unbound.conf(5):
"The zone of the query is determined by examining the nameservers for
it, the zone name is used to keep track of the rate."
So if we have a ratelimit of 1000, does that mean
Dear Folks,
On 15/12/16 09:40 +0100, W.C.A. Wijngaards via Unbound-users wrote:
Features
- Added generic EDNS code for registering known EDNS option codes,
bypassing the cache response stage and uniquifying mesh states. Four
EDNS option lists were added to module_qstate
