4

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 app1.domain.com, so i want to add *.domain.com 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?

2
  • 5
    Generally speaking, any time you answer a question with "/etc/hosts" the "real answer" is to use DNS. >smile< Jan 28, 2010 at 12:58
  • loved your comment ^_^
    – Shoaibi
    Mar 25, 2010 at 9:16

3 Answers 3

8

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

3

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

0

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.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .