I'm new to the mailing lists so I hope it's the correct way to report a bug.
There's an issue with resolving domain names. I'm connecting an stunnel client to a server that sits on a computer which IP address is dynamic. Therefore I'm using a dyndns for the IP address of the server. When the IP address of the server is changed, the stunnel client doesn't update the name resolution of the dyndns name and tries to connect to the old IP which is of course unsuccessful. This can be resolved only by exiting and starting stunnel client again when a new domain name resolution is made.
Would it be possible to add a functionality to the stunnel that wouldn't cache the name resolution but try to resolve the domain names every time there's a connection request?
I'm using a Windows OS for both server and client, not sure if that makes a difference.
Thanks! David
Hi,
Add "delay = yes", without quotes, globally or per-service (on client stunnel). It's enough.
You only need to have in mind that the dynamic DNS provider do its best but all depends on the whole DNS network, so, even setting this on stunnel client service, are needed about 1, 2, 3 minutes, or even more, to propagate the new IP and with the luck that DNS providers don't cache the for long times the resolved names, if you don't use your own DNS server.
Regards.
P.S.: the time I said is, more or less, what No-IP "lags" to propagate, according to my experience with it.