Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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'm looking to create a domain called "" to join computers to. I need to make a domain controller for this domain in Windows Server 2012, this is my first time. What are the steps? So far I have researched and pulled together steps from different sources but I don't know if I'm missing any steps or if some steps don't apply to me. Please review:

  1. Register ""

  2. Configured server IP to be static (say ----Should I set the preferred DNS servers in this configuration to the same thing they were before? Im guessing that's my ISP's DNS servers and I should leave it the same as before?

  3. Installed ADDS and DNS roles.

  4. Add domain to Forward Look Up Zones: DNS Manager -> Forward LookUp Zones -> New Zone for "" (primary)

  5. Create A record for subdomain: Refresh -> Forward Look Up Zones -> -> create New Host(A or AAAA) record for "" ----- Is this supposed to point to the static IP I just made in step 1?

  6. Create A records for nameservers: -----What IPs should the name server A records point to? Same server IP as ""?

  7. Create NS records for nameservers: Refresh -> Forward Look Up Zones - > -> Properties -> NameServers tab -> Add -> Resolve -> Add -> Resolve

  8. Add nameservers in Internet Registrar settings

After all this can I join computers to domain?

share|improve this question

migrated from Oct 29 '12 at 8:24

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

up vote 2 down vote accepted

You should own the domain you're using, so in your example, you need to own You do not, however, need to create any DNS entries for it, either on your internal LAN or externally.

If you're installing AD from scratch then you can just go ahead and install the AD Domain Services role on your server. You just supply the domain name as the AD domain name.

You'll be prompted to install DNS as part of the AD installation process, say yes to this offer and it should install DNS and create the appropriate entries for you. DO NOT try and use the ISP's DNS for your domain controller or your clients. You can have your local DNS forward requests to the ISP DNS but the sever and its clients need to use the AD server's own DNS server to find each other for your local network to work properly.

While its possible to do the DNS configuration by hand, if you've never installed AD before then I'd strongly suggest letting the AD install process do this for you then looking at what its done afterwards.

This is all you need to do to create a domain that you can join computers to in a network. There's a lot of "best practice" stuff you should really be doing as well (you really should have more than one DC for a start) but this is the basic 'get you started' level.

You might find this question useful for AD background too.

share|improve this answer
Thank you for the reply. I already tried letting the AD wizard to do everything for me but I got a warning that I didn't feel comfortable ignoring as I didn't know if it applied or not. The warning was "The delegation for this DNS server cannot be created because the authoritative parent zone cannot be found or does not run Windows DNS Server." – Vazgen Oct 29 '12 at 17:42
If I understand correctly, I can ignore this warning because I do not care if resolves to my server, I'm only concerned about to resolve. Am I understanding correctly? – Vazgen Oct 29 '12 at 18:21
Yes you are right @vazgen This is the server giving you a warning so you can check things are behaving as expected, rather than an error as such. See… – RobM Oct 29 '12 at 18:54
Thank you but I'm not able to join a different computer to my "" domain name it says the domain controller cannot be contacted. What am I still missing? – Vazgen Oct 29 '12 at 19:03
The domain controller is running on a VM on my client computer. Perhaps this is a misconfiguration of the virtual switch? I have the "preferred dns server" on the network adapter properties on the domain controller VM set to itself ( However ping resolves to an IP address that is not If I set these same configurations for the virtual switch network adapter on the client, ping does not resolve to anything. please help? – Vazgen Oct 29 '12 at 20:08

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.