U Turn NAT from External to Internal with FQDN Object

Showing results for 
Search instead for 
Did you mean: 

U Turn NAT from External to Internal with FQDN Object

L1 Bithead

I know how to create a standard U-Turn NAT from outside to inside and that works fine as long as the INTERNAL object is an IP Netmask address.  On the NAT Policy Rule the Original Packet is a static IP on my external facing range.  The Translated Packet needs to point to a device that will have a dynamic IP.  This is a mobile cart that can travel to different subnets on my network.  The problem is I can create an Address Object using a FQDN designation.  But I cannot put that into the Destination Address Translation section.  If I create an Address Object with the cart's current IP and assign that to the NAT Destination Address Translation and test my rules and all is fine.  I tried to "trick" the firewall by converting the IP Netmask to a FQDN object;  this did not work.  Again this is not a matter of assigning a static IP to the device.  One group might use it in a switch with a subnet and then move it to an area with a subnet.


L7 Applicator

Where is the DNS server that returns the public address for the resource?


Perhaps you can use DNS proxy and static rules to give the internal address to internal users instead.




Or setup split DNS so the u-turn is not needed.

Steve Puluka BSEET - IP Architect - DQE Communications (Metro Ethernet/ISP)
ACE PanOS 6; ACE PanOS 7; ASE 3.0; PSE 7.0 Foundations & Associate in Platform; Cyber Security; Data Center
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!