10-30-2013 04:42 PM
The NAT rule can be specified for Destination Address Object, which can be configured to be an FQDN address object. This setting should work as long as the Palo Alto is able to do a FQDN lookup succesfully for the specified FQDN.
However, as long as the FQDN resolves to the same IP you may not be able to have them translated to different Inside servers.
The reason being, if multiple FQDNs resolve to the same Public IP, having different NAT rules will create a conflict when setting the NAT rule. The firewall irrespective of whether we have the FQDN or actual IP will still store the IP in the running config, having multiple NAT rules with the same Ip will create a conflict.
10-30-2013 04:42 PM
The NAT rule can be specified for Destination Address Object, which can be configured to be an FQDN address object. This setting should work as long as the Palo Alto is able to do a FQDN lookup succesfully for the specified FQDN.
However, as long as the FQDN resolves to the same IP you may not be able to have them translated to different Inside servers.
The reason being, if multiple FQDNs resolve to the same Public IP, having different NAT rules will create a conflict when setting the NAT rule. The firewall irrespective of whether we have the FQDN or actual IP will still store the IP in the running config, having multiple NAT rules with the same Ip will create a conflict.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
