For inside users to access these servers via the public IP, you need to set up "destination NAT" in the PIX, where the PIX will see traffic destined for 188.8.131.52 and change the destination to 172.16.2.10.
The commands you specify above are exactly what's needed. This tells the PIX that if you see a packet on the inside interface for 184.108.40.206, change it to 172.16.2.10 and send it to the dmz interface.
What you could also do, if your DNS server is on the outside interface and it resolves to 220.127.116.11 when your users browse to these servers, is change your existing statics to:
static (dmz, outside) 18.104.22.168 172.16.2.10 dns netmask 255.255.255.255
staic (dmz, outside) 22.214.171.124 172.16.2.11 dns netmask 255.255.255.255
which tells the PIX that if it sees a DNS reply come through that has 126.96.36.199 in it, change it to 172.16.2.10, this way your users can browse to it via its public name and they won't have any idea what IP address they're actually connecting to.
This'll only work if the DNS server is on the outside though, otherwise use "Destination NAT" like you have done with the 2nd set of commands.
Your config is correct. However, don't forget that inside users must have some form of NAT on their way out to the DMZ. When going from high to low, the source address must always have some form of NAT configured. This can be accomplished with [static], [nat 0], or [nat][global].
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...