I am going to do my best to explain the issue clearly.
We have an ASA5510 Cisco Firewall. On that firewall we have three interfaces. Outside, Inside, and DMZ.
We currently have a FTP site that all of our internal and external employees\clients use. It is on a web server on the DMZ. The web server is a standalone Windows 2000 server the only thing loaded is IIS for the FTP site.
The website is DMZ address is 192.168.251.11 and the outside address is 184.108.40.206 and there is a static in the firewall that takes care of the outside to DMZ translation. So when people outside hit ftp://www.ourdoaminname.com
they go to 220.127.116.11 and get prompt with a login box.
Outside access to the FTP site works just fine!!!!!!
The real issue is inside access. When an internal user goes to ftp://www.ourdoaminname.com
it never connects and ends up in error. If you ping ftp://www.ourdoaminname.com
you get the outside IP address not the address on the DMZ. Now if I go to ftp://192.168.251.11
from inside I get the login prompt and I can get right into the site. I know that our internal folks could just use the IP addresses but I have the extreme need to make this seamless. I would like everyone to look and work the same internal and external. Plus when I change the site later and I can just change DNS as opposed to IP addresses on 80 machines.
Is there any way to use my internal DNS server to redirect my clients to the DMZ address if so how do I do it? Secondly if not is there something the firewall can do to perform the redirect or translation?
We own a domain name name for