Tell me more ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.
up vote 0 down vote favorite

Scenario is a developer build out in VirtualBox. I am looking to combine the DC with NAT (2 NICs, one internal and one NAT) running server core 2012. A key goal is to hide the (internal) DEV domain from the outside world while still allowing any DEV VMs on the internal domain access to e.g. Windows Update.

Is this as simple as adding the NICs to the 2012 VM, installing the OS and then following one of the tutorials for creating a domain controller? Are there any steps I should take to prevent other physical hosts from seeing the DEV domain?

Thanks in advance for any insights, suggestions, etc.

share|improve this question

migrated from serverfault.com Dec 3 '12 at 2:25

1 Answer

up vote 1 down vote accepted

You want to prevent the external adapter from dynamically registering itself in DNS before you dcpromo, otherwise you're going to run into connectivity issues with clients inside of the private network.

This Windows 2000 Server article is still relevant in this case.

share|improve this answer
Thank you! I found a PS script to do this (since it's server core): social.technet.microsoft.com/Forums/et-EE/ITCG/thread/… Will mark as answered once it's working. Thanks again. – Jason Weber Dec 9 '12 at 1:34
While the script above runs without error it does not seem to actually set the adapter's FullDNSRegistration status to false as seems to be desired if I understand the post. – Jason Weber Dec 9 '12 at 2:26
After re-reading the original article you posted (thank you) I'm wondering if it wouldn't be simpler to set up the DC with a single, internal NIC and then add the second NIC after promotion. Any thoughts on this? – Jason Weber Dec 9 '12 at 2:30
It will still auto-register that second NIC eventually. Multi-homed domain controllers are messy. Really consider just not doing it at all. – MDMarra Dec 9 '12 at 2:48
Point taken. Maybe I asked the wrong question initially. What is the best way to achieve the primary goal of running a domain on an internal network and still providing external access for the DEV VMs on the network? And thanks again for the help / guidance so far. – Jason Weber Dec 9 '12 at 16:41

Your Answer

 
discard

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.