Hi Alex,
You can try this:
1) Create an address object:
So you can run a DDNS agent (best option is to install it on the actual server) on the trust zone which constantly will be mapping/updating your outside dynamic IP to the www.myserverip.com DNS name.
More info here:
2) Create a NAT policy for the internal server to be reachable from the outside. Really it is just a port forwarding
3) create a security policy for the server
Thx,
Myky
you could try mapping your external IP address (assuming it is dynamic) to a DynDNS service, then create a FQDN object you can use in the NAT policy
me.me.me is an example of an FQDN object you could have set up
it would represent a dyndns URL mapped to your external IP address
typically this would be a url specific to your dyndns provider, like me.dyndns.org which is dynamically mapped to your external IP, so when your ISP assigns you a fresh IP, dyndns will change the A record assigned to your url (me.dyndns.org), the PAN will refresh it's dynamic objects periodically (you could script a forced refresh if needed) and the NAT rule will be changed accordingly
An FQDN object allows you to rely on DNS resolution to populate an IP address in your policies rather than manualy setting a static ip, in case the IP tends to change a lot:
Hi Alex,
You can try this:
1) Create an address object:
So you can run a DDNS agent (best option is to install it on the actual server) on the trust zone which constantly will be mapping/updating your outside dynamic IP to the www.myserverip.com DNS name.
More info here:
2) Create a NAT policy for the internal server to be reachable from the outside. Really it is just a port forwarding
3) create a security policy for the server
Thx,
Myky
