I have a server on a dynamic ip address. If the ip address changes I can no longer establish connections. Although my certs refer to a dns name rather than an ip, if the dns is updated to reflect the new address, ssl fails. If the application is restarted, everything works with no changes. It appears that the application does a name lookup at process startup and uses the ip address found persistantly somehow, rather than doing the lookup at the time the connection is attempted.
Why does this happen and how can I correct this behaviour?
- ip changes prevent ssl jeff sacksteder
- RE: ip changes prevent ssl David Schwartz
