We have had this weird problem for a long time where sometime DNS resolution 
will fail with this error:

Error resolving 'domain name printed here': Neither nodename nor servname known 

Today I found out that this will happen when stunnel get 2 calls for the same 
outgoing endpoint very fast one after the other.

One call will work no problem. But if you do 2 one after the other then the 
second one and all other subsequent will fail.
Wait a bit and try again, the first one will pass and then others will fail.

DNS resolution on the server (linux) itself work without problem, nslookup in 
loops no problem. But with stunnel we always have the problem.

The only working solution is to add a record to the server host file.

Any idea ? Could this be a bug in stunnel ?



stunnel-users mailing list

Reply via email to