Access to internal servers using public IP address

Question

I have an ASA5540 on 8.2(5) and I am setting up a Guest Wireless network that is on the same interface as our corporate user network, but is completely segregated and uses Google Public DNS (8.8.8.8). I have this all set up, but the only thing I can't get is users on this network can not access our external facing DMZ web servers.
1) I have attempted to use DNS doctoring:
static (dmz,outside) external_ip internal_ip netmask 255.255.255.255 dns
(the rule was already in place, I just checked the dns box)
and when I do an nslookup, it does resolve the internal ip but the page wont load. If I type the internal IP into a browser, the page loads (I set up a rule to allow access from the guest network to the dmz network).
2) I wrote 1:1 static nat rules going the other way:
static (outside,dmz) internal_ip external_ip netmask 255.255.255.255
and pages still could not load.
From what I have read, either of these solutions should work, but neither of them do. What am I missing from this setup?

Answer 1

I contacted Cisco Support and they helped me with this.
First, I needed to create a static NAT rule on the internal interface to DMZ for the Guest network:
static (internal,dmz) WiFi-Guest WiFi-Guest netmask 255.255.255.0
After that, I could add in another static NAT rule for my DMZ servers on the internal interface in addition the the existing rules on the external. i.e.
static (dmz,internal) external_ip internal_ip netmask 255.255.255.255
Once both of those were complete, the pages could load from the DMZ, but not from the rest of the Internal network