Hi, stunnel 4.26 solves a number of issues running on FreeBSD. However, a stunnel client still has a problem reconnecting to a host with dynamic DNS service after the host IP has changed. Stunnel client seems unaware of the host update, pointing the dynamic DNS name to the old outdated IP. In order to get reconnected to the host, I have to create a cron script to detect the IP change and restart stunnel on the stunnel client. My client conf file has the following:
[1873] accept = 1873 connect = hostname.dynaip.org:1873
The ip of hostname.dynaip.org changes at a random interval.
Please help.
Adamosn H
Adamson H wrote:
Hi, stunnel 4.26 solves a number of issues running on FreeBSD. However, a stunnel client still has a problem reconnecting to a host with dynamic DNS service after the host IP has changed. Stunnel client seems unaware of the host update, pointing the dynamic DNS name to the old outdated IP. In order to get reconnected to the host, I have to create a cron script to detect the IP change and restart stunnel on the stunnel client. My client conf file has the following:
[1873] accept = 1873 connect = hostname.dynaip.org:1873
The ip of hostname.dynaip.org changes at a random interval.
The solution is: delay = yes
Best regards, Mike
-
Adamson H -
Michal Trojnara