Re: error: outgoing tcp: bind: Address already in use

Hi Nick, IIRC, unbound does a “bind before connect” on sockets, which requires a local port to be completely unused [1] to be used by bind. Unbound 1.6.4 should fix this by setting SO_REUSEADDR on outgoing ports - please give it a try. Kind regards Quirin [1]

Re: error: outgoing tcp: bind: Address already in use

Hi Nick, The config number for outgoing tcp is likely too low. outgoing-num-tcp: 1000 Also, you may be running out of port numbers, perhaps this causes the 'bind a tcp socket returns errno Address already in use', because the choice of port number was left to the kernel? Unless you force a

error: outgoing tcp: bind: Address already in use

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

Re: Unbound Srvfail cache

Including unbound users. -- Respectfully Mahdi A. Mahdi From: Mahdi Adnan Sent: Thursday, July 6, 2017 10:49 AM To: W.C.A. Wijngaards Subject: Re: Unbound Srvfail cache Hi Wouter, The issue does scale for more than 15 minutes,

ratelimit: exactly what is counted before limit applies?

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

Unbound Srvfail cache

Hi folks, We have a situation here with Unbound, during internet outage for an hour or so, Unbound keeps replying with server servfail for valid domains even after it gain access to internet, to fix this, i have to reload or restart Unbound. This happens every time we lose internet for more