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

I work for a studio that spends its days developing websites. There are often multiple people working on a project at once. I would like to be able to let people share what they are working on with the office in a standardized way.

I was thinking the url would work like this


for example

Is there a way I can setup an internal DNS server that can recognize the .dev extension, parse out the user and use that to reroute the request to their machine IP where apache is waiting to respond with the correct vhost setup?

share|improve this question
up vote 3 down vote accepted

You probably can't do it all with DNS, but it sure seems like it would be trivial to setup a .dev domain with a wildcard record that sends all traffic to an HTTP proxy that routes requests to the proper machine.

share|improve this answer

If your users receive their IP from DHCP, you could setup the DHCP server to create a dynamic DNS record to register each machine's name in a .dev domain.

Since I think you can't make DHCP create the wildcard records you need, maybe you can create wildcard-records that are CNAME aliasses which point to each user's dynamic-DNS record.

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.