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 have a server on which we host private services. These services can also be access from rest of the world but there is slight difference on application level based on from which IP request came.

Applications run on subdomains like, so i want to add * to exception somewhere and point it to our VPN IP instead of public. /etc/hosts is an overkill as there are 25 client systems at this office and further more i would have to update everyone's /etc/hosts everytime we launch a new app. I am looking for more generic and one time solution.

Could DNS be my solution? but even in that case won't i have to add a new entry everytime a new app is launched? (which is much better than adding it to 25 machines though but still...)

What do you suggest?

share|improve this question

migrated from Jan 28 '10 at 7:19

This question came from our site for computer enthusiasts and power users.

Generally speaking, any time you answer a question with "/etc/hosts" the "real answer" is to use DNS. >smile< – Evan Anderson Jan 28 '10 at 12:58
loved your comment ^_^ – Shoaibi Mar 25 '10 at 9:16
up vote 8 down vote accepted

DNS is the solution here. That's what it was set up to do.

share|improve this answer

Yes, use DNS. If all the services are on the same machine you can add a wildcard record for * pointing to that IP.

share|improve this answer

This is a great use for DNS zones. Lots of places have an internal zone and an external zone, so if you're coming from an internal IP, you get one set of addresses and everyone else gets another.

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.