I'm assuming that you are hosting your TKL OpenVPN appliance on Amazon. If so, then you will get a new public IP on reboot (IPs are asigned via AWS's DHCP). If you have a domain name assigned by HubDNS then although HubDNS is preconfigured with a short TTL, sometimes some DNS providers (ISPs seem particularly bad) overrule this and have slow DNS updates.
The best workaround for that whole situation is to apply an AWS Elastic IP. They are essentially a static IP and are free (one per server) when attached to a running instance. If your server is regularly stopped/offline then check the prices on AWS to see if it's worth the cost to you...
Thanks for posting back
I'm assuming that you are hosting your TKL OpenVPN appliance on Amazon. If so, then you will get a new public IP on reboot (IPs are asigned via AWS's DHCP). If you have a domain name assigned by HubDNS then although HubDNS is preconfigured with a short TTL, sometimes some DNS providers (ISPs seem particularly bad) overrule this and have slow DNS updates.
The best workaround for that whole situation is to apply an AWS Elastic IP. They are essentially a static IP and are free (one per server) when attached to a running instance. If your server is regularly stopped/offline then check the prices on AWS to see if it's worth the cost to you...