Destination NAT rule translates to random IP

Destination NAT rule translates to random IP

18798
Created On 09/07/19 03:05 AM - Last Modified 07/14/25 18:44 PM


Symptom


  • There is Destination NAT rule configured on Firewall that has Pre-NAT address as an FQDN in Original Packet Tab.
  • After the reboot from 9.0 upgrade, NAT rule translates the Destination address to random IP address.
  • A commit will fix the issue but a new DNAT rule with same details will run into the same issue and will require another commit for fix.
An FQDN 'updates.paloaltonetworks.com' that resolves to IP 199.167.52.141, is used in the following NAT rule.
Destination NAT rule
admin@Lab> show running nat-policy

"InboundNAT-2; index: 2" {
        nat-type ipv4;
        from L3-Untrust;
        source any;
        to L3-Untrust;
        to-interface  ;
        destination 199.167.52.141;
        service 0:any/any/any;
        translate-to "dst: 3.3.3.3";
        terminal no;
}
Traffic to destination 'updates.paloaltonetworks.com' is supposed to be translated to IP 3.3.3.3 but, after the firewall is rebooted or if this is newly added NAT rule then the firewall will translate to random IP.
admin@Lab> test nat-policy-match source 172.17.188.10 destination 199.167.52.141 protocol 6 destination-port 23

Destination-NAT: Rule matched: InboundNAT-2
199.167.52.141:23 => 202.170.55.144:23

admin@Lab>




 


Environment


  • Palo Alto Networks Firewall
  • PAN-OS 9.0.x
  • Destination NAT utilized with pre-NAT FQDN updates.paloaltonetworks.com


Cause


In PAN-OS 9.0, if Destination NAT rule has Pre-NAT address as FQDN in original packet tab then it will not work with Translation type Static.

Resolution


If firewall is upgraded to PAN-OS 9.x or if it is running PAN-OS 9.x then make the following changes to Destination NAT rules.
  1. If Pre-NAT address in Original Packet TAB is FQDN then select the translation type Dynamic.
  2. If the Translated address is FQDN, an address object, or an address group then select the translation type Dynamic.
Changing to type Dynamic
  1. After changes, it started translating to correct IP address. This will continue to work fine even after the firewall reboots.
admin@Lab> test nat-policy-match source 172.17.188.10 destination 199.167.52.141 protocol 6 destination-port 23

Destination-NAT: Rule matched: InboundNAT-2
199.167.52.141:23 => 3.3.3.3:23

admin@Lab>

 


Additional Information


NAT Translated Packet Tab

Destination NAT rule translates to random IP



Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMkdCAG&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail