Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Release Notes: Junos OS Release 22.4R3
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Network Address Translation (NAT)

date_range 08-Nov-23
  • Support to retain existing NAT session with destination NAT (SRX Series)—Starting in Junos OS release 22.4R3, with FQDN based Destination NAT, we support to retain existing NAT sessions even when the DNS resolved IP address changes for the Destination NAT Pool. To retain the existing NAT sessions, you can enable session-retain at [security nat destination pool pool-name] hierarchy. When session-retain is enabled, FQDN based destination NAT sessions remain in the session table, and cleared only upon connection termination from clients, or timeout due to sessions being inactive, or when sessions are explicitly cleared by the user through CLI.

    Common DNS cache for NAT and Policy: The NAT and configured policy FQDNs use a single cache. The use of the single cache helps avoid packet drops if you've configured the same FQDN in the policy and NAT.

    [See pool (Security Destination NAT).]

footer-navigation