Hi Carlo ,
ip nat outside source lis/route-map - translates the source when flow is entering the outside and going to inside
ip nat inside destination - translate the destination when flow is entering the outside and goint to inside
If it's simple to remember : the command ip nat tells you were is the host/network that will be translated.
Thinking again about it.......
I think the "right" syntax for destination address translation of packets entering from outside and going to inside should be
ip nat outside destination instead of "ip nat inside destination"
After all here we are translating the Inside global (IG) address into Inside Local (IL) address as destination for a packet entering from outside i/f...
Does it make sense ?
As far as I know "ip nat outside destination" is not available. Destination keyword is only available on ip nat inside and is used for load-balancing.
There are 2 types of nat : static and list ( acl and route-map ). The main difference between them is that static creates a bidirectional translation. This means that , unlinke the 'list' nat, the packet can be originated on any interface (outisde|inside).
In your case you need to configure a static nat. IOS will DNAT in case of a packet arriving on the outside interface with the destination of Outside Global according to your nat statement
Thanks Dan for the answer....
The spirit of the question asked to clarify doubts about terminology: if I understand correctly the configuration statement ip nat inside destination (used for load-balancing ....) perform translation of packets' destination address entering from outside interface (following configured rules of course)... that address is mapped to a 'real' server address chosen into a 'rotary' servers pool ....
Now, if that is right, the router is translating the inside global address in an inside local (the address of the choosen sever in the pool) ... so, based on this reasonings, I was thinking about the syntax ip nat ouside destination instead of 'ip nat inside destination'....