Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I currently have my Cisco ASA 5505 firewall configured to forward port 80 from the outside interface to a host on my dmz interface. I also need to allow clients on my inside interface to access the host in the dmz by entering the public ip / dns record in their browsers. I was able to do that by following the instructions here, resulting in the following configuration:

static (dmz,outside) tcp interface www www netmask 
static (dmz,inside) tcp www www netmask

(Where is my public IP and is the IP of the dmz host)

This works great except for the fact that my network has a dynamic public IP and this configuration will therefore break as soon as my public IP changes. Is there a way to do what I want with a dynamic ip?

Note: Adding an internal DNS record won't solve my problem since I have multiple dmz hosts mapped to different ports on the public IP.

share|improve this question

3 Answers 3

I wondering why the clients behind the inside interface have to enter the Public IP, wouldn't it be easier for them to use the private IP of the DMZ host. Then you could make a normal nat eg.

static (dmz,inside) tcp (Inside IP Range) www www netmask

As far as I get it the problem in your case is, that when a client makes a DNS request, the DNS server from the internet gives him the current outside IP Address of the ASA back. After that the Client tryes to Connect to that IP, so a packet is sent to the Outside interface and has to return to the DMZ interface.

Cisco Firewalls have one problem, per default they never give a package out of the same interface they get it in. Cisco solved that since 7.2 release with the follow cli command:

ASA(config)# same-security-traffic permit intra-interface

so as far as I understand you bypassed exectaly that behavior by adding the second static NAT. In my opinion if you remove the second NAT entry and active the same-security-traffic option, it should work.

But I would strongly suggest that you buy a public IP :-)

share|improve this answer
Cisco includes 'DNS Doctoring', also called DNS rewrite, which rewrites responses from an external DNS server to an internal address so packets don't have to hairpin the outside interface. It requires a DNS record though. Not sure if it would work with a Dynamic DNS record, since the rewritten result is cached. –  Martijn Heemels Mar 27 '10 at 0:22

I think the only answer you're going to get is no.

There is no way an ACL or a NAT statement can account for a changing IP address, it just can't happen.

share|improve this answer
That's strange. My old firewall, a WatchGuard Firebox, did this just fine. It was actually the default behavior. –  Joseph Sturtevant Jun 9 '09 at 18:31

Actually, you could make it work with internal DNS changes.

Let's say for example you have several services:

static (dmz,outside) tcp interface www www netmask
static (dmz,outside) tcp interface smtp www netmask
static (dmz,outside) tcp interface ftp www netmask

Let's say you have pointed using a dynamic DNS provider to your ever-changing public IP address.

You can run an internal name server pointing at, say,, and use the following:

static (dmz,inside) tcp www www netmask
static (dmz,inside) tcp smtp www netmask
static (dmz,inside) tcp ftp www netmask

Then you point your clients at your internal name server and have at it.

The caveat is that for each new service you add, you'll have to set up a static for the inside network and a static for the outside interface, as well as allowing that in the ACLs from both inside and outside. However, when your public IP changes, your traffic will still go where you want it to go.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.