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

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have multiple servers running on our network using a ASA 5510 as the firewall and router.

NAT is used to give the servers their external IPs.

When a request made externally using the external IP it works find such as just going to the webpage http://externalip/ but when a request is made internally using the external IP it fails so if you were to be on an internal server and curl http://externalip/ it will timeout. Though if you use the internalip it will work. I am thinking this a routing issue of not being able to go out on an external ip and come back in. Any suggestions would be appreciated.

share|improve this question
up vote 3 down vote accepted

You are correct, that is not possible. You could set up internal DNS to use the same hostnames (e.g. You have an internal server on that is NATed to Externally, resolves to Internal DNS (possibly using split horizon if you already run your own) would allow you to do this.)

share|improve this answer
poor mans way could be to use a hosts file on your internal clients – Fergus Jul 12 '11 at 4:59
Indeed. The tough part about that is distributing, but possible with a config management system such as Puppet or Chef. – Scott Smith Jul 12 '11 at 19:49

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.