Super User is a question and answer site for computer enthusiasts and power users. 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

Given the following requirements:

1 - a virtual dev domain

2 - all VMs can access to the Internet (e.g. for Windows Update)

3 - other physical hosts cannot access the virtual network

What is the best way to achieve this?

In the recent past I put everything on a single VM. This usually worked, but also resulted in what felt like a lot of rework each time the VM needed to be rebuilt. Also, the consensus view seems to be to avoid multi-homed domain controllers.

Originally, I ran separate VMs for a domain controller, a NAT server and any other development servers. This resulted in a practical minumum of 3 VMs running at a time which seemed high.

Is there a better way to tackle this? Is there a preferred configuration among developers for this case?

share|improve this question

closed as not constructive by Ƭᴇcʜιᴇ007, Mokubai, ChrisF, Canadian Luke, Tog Jan 12 '13 at 20:52

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

I'm not sure which virtualization technology you are using, but VirtualBox's NAT network should give you the network configuration you're looking for. All hosts will have access to the internet through the host's network connection, but the machines cannot be accessed from outside the virtual network unless you setup port forwarding through the virtual NAT.

share|improve this answer

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