Nat ID's are not used for deciding the priority, they are only used to match the corresponding global statements. If you have multiple nat and global statements, they are matched from top to bottom, so when you try to ping the DMZ, since you have any any access-list, it falls in the first nat statement, but te corresponding global for it is the global (outside) and the packet is dropped.
When you remove the first nat statement, then the DMZ traffic hits the correct nat statement, but then the inside to outside traffic is blocked, since you have removed the nat for it.
What you need to do is, specifiy very strict ACL's, lets say your dmz is 192.168.1.0/24 and inside is 10.1.1.0/24, then you would just need:
nat (inside) 75 192.168.1.0 255.255.255.0
global (outside) 75 interface
global (dmz) 75 interface
Thats it and it would work like a charm, you can have multiple global statements for the same nat statement.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...