Best practice to account for public IP address change within policies

Good morning,

We currently have policies set up to allow customer connections to our internal remote support (ScreenConnect) and remote monitoring/remediation (Automate) servers. I am trying to determine the best method to account for the possibility that a customer's public IP might change through their ISP, so that the policies would not have to be modified manually. If using FQDN instead of IP, how often will the Firebox resolve the address, and is this a setting that can be changed? I am also looking into dynamic DNS and the Firebox's capabilities, but wanted to reach out to see if anyone had any thoughts/suggestions regarding the best course of action to pursue. Any advice would be greatly appreciated!




Sign In to comment.