To follow up on my rant from above - just whose silly-poot idea was it to use hardcoded IP addresses instead of a more dynamic hostname in databases and scripts?
After I have determined that the copper ADSL line for the ftp server was on the fritz, I decided to swing the whole shebang over to a fiber line (with a better SLA). Copper ADSL will have a very low priority for repair this time of the year anyway.
So the switchover was done, ftp server accepts my logins etc. Let $support know all is cherry.
Their one script was still not connecting despite changing the hardcoded IP in the production database. After asking and confirming that there is only one table that holds the IP for the FTP server, I digged into the recalcitrant script - and discovered that it also have an hardcoded IP.
Fixed it, tested it. Success.
Support was not too thrilled in updating a couple of servers…
So guess what I’ll also be doing next year? Getting a better system implementes that does not use hardcoded IP adresses.
And getting our telco to fix their line. Maybe it is time to ditch copper and move over to fiber…