Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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 host several web based applications outside of intranet. The URL's to these applications are long, complex and overall not user friendly. Ex:

http://hostingsite:port/approot/folder/folder/login.aspx <-- (production)
http://hostingsite:port22/approot/folder/folder/login.aspx <-- (dev)
http://hostingsite:port33/approot/folder/folder/login.aspx <-- (test)

I'd like to create an internal DNS entry to allow users to access these sites with ease. Ex:

http://prod  --> http://hostingsite:port/approot/folder/folder/login.aspx
http://dev --> http://hostingsite:port22/approot/folder/folder/login.aspx

I'm not familiar with the DNS process and setup, as far as I know a DNS can only be redirected to an IP, but not to subdomains for directory paths as described above? Is this a correct assumption?

I am thinking for throwing up an internal webserver that will listen to the internal DNS entries and redirect to the external sites.

http://prod --> [internal webserver] --> redirect --> http://hostingsite:port/approot/folder/folder/login.aspx

Is there a better way to do this?

share|improve this question
up vote 1 down vote accepted

You are correct. DNS can only resolve the domain part but is unaware of any kind of path structure. Therefore the esiest solution would be a webserver to redirect or reverse proxy, like you proposed.

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.