Lets come to conculsion first before answering your question about destination NAT
Destination NAT is always inbound traffic . When outside network users wants to access inside network resources it's (outside to inside)
Example : Assuming you have hosted a application in your internal network and the requirement is wants to access application from internet in this case we will configure destination NAT with public ip provided by ip with application hosted server private ip command in cisco ISR router is as below
IP nat inside source static 10.0.0.3 126.96.36.199
Users from internet will initiate traffic with destination ip 188.8.131.52 . Traffic will hits ISR router and it's translated packet ip header to private ip and enters into internal networks and access the application and responce will fallow same path ..
As you stated in your question any packet intiàted going from inside to outside => is always considered as souce NAT command is as fallow
IP nat inside souce static "private ip "public ip"
IP NAT inside source vs IP NAT outside source
IP NAT inside source
IP NAT outside source
On Cisco IOS routers we can use the ip nat inside sourceand ip nat outside source commands. Most of us are familiar with the ip nat inside source command because we often use it to translate private IP addressses on our LAN to a public IP address we received from our ISP.
What about the ip nat outside source command? Does it work in the same way as ip nat inside source?
This is the difference between the two commands:
ip nat inside source:
Translates the source IP address of packets that forwards from inside to outside.
Translates the destination IP address of packets that
Forwards from outside to inside.
ip nat outside source:
Translates the source IP address of packets that forward s from outside to inside.
Translates the destination IP address of packets that travel from inside to outside