[BUG?] resolve ftphostname again after forced reconnect

[Thetimetraveler]

Hello
today I want to share a little experience I made with the ftp module.


I have a ftp server running at home behind a router. The router has a static hostname from dyndns so I could connect it at any time where ever I am.
However when I transfer files to my ftp server and the connection gets interrupted and the IP-Adress changes (e.g. the forced reconnect at night) Salamander won't continue the transfer because it is trying to connect to the old ip address over and over again instead of just resolving the hostname again and getting the new ip.
only when I cancel everything and connect again it works, but it is very bad if you want to transfer something over night, because then you can't interfere.

Thats maybe not a real bug but at least something, probably nobody thought of.

My suggestion would be to have the host name resolved again if the reconnecting attempt fails 2 times or include the resolving in the reconnect procedure right away.


Thank you in advance.


Sincerely, Time