Agree use DNS doctoring
Note this replaced the alias command, you need a to write a Static the WRONG
way round and put the "dns" on the end of the command.
Syntax
static (inside,outside) {Inside IP} {Outside IP} netmask 255.255.255.255 dns
Here is a working example with the equivalent OLD alias command.
Static (inside,outside) 10.254.254.10 123.123.123.123 netmask 255.255.255.255 dns
alias (inside) 10.254.254.10 123.123.123.123 255.255.255.255
or as stated above create a DNS forward lookup zone on your server called abc-web-server.com and create a A (host) record called www that points to the internal IP address of your web server.
Main Topics
Browse All Topics





by: JasonTracyPosted on 2008-10-13 at 06:25:19ID: 22702149
There are two options I know of. One is the "DNS Rewrite" command. This is supposed to see outbound DNS requests and rewrite them so the reponse gives the client the internal IP address. The option for this is a checkbox if using the GUI when you setup the NAT for the webserver. /products/ ps6120/ pro ducts_conf iguration_ example091 86a0080796 8d1.shtml
Here is a link to Cisco that discusses it, they call it "DNS doctoring" here:
http://www.cisco.com/en/US
The other option (the one I use on my network) is to setup the same domain on your internal DNS server, but instead of the public addresses, just put the internal addresses.
Either way, the goal it to give your clients the web server's true internal address instead of its NAT address outside the firewall.