Step-by-Step: When creating a new Root Level Domain Controller you get the message “A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found”

by vivek 11/12/2012 11:30:00 PM

This is the 6th post in this series and today I am working on resolving a warning which appears when you are trying to create a new forest in a new network.

image

 

Let us walk through the above error first and then the steps to resolve it:

Step 1: Installing Active Directory Domain Services


  • I created a new VM and installed Windows Server 2012
  • In Server Manager –> click on Manage –> click Add Roles and Features Wizard –> click Next
  • Under Select installation type, select Role-based or feature-based installation –> click Next


    image

  • Under Select destination server –> click Next


    image

  • Under Select server roles –> click Active Directory Domain Services
  • Under Add features that are required for AD DS –> click Add Features –> click Next


    image

  • Under Select features –> click Next –> click Next –> click Install


    image

  • Finally the Installation progress window shows, installation completed successfully but Configuration required


    image

  • Click Promote this server to a domain controller, this starts Active Directory Domain Services Configuration Wizard
  • Under Deployment Configuration –> click Add a new forest, type Root domain name: dotnetscraps.com –> click Next


    image

  • Under Domain Controller Options, enter Directory Services Restore Mode (DSRM) password –> click Next


    image

  • Here you are prompted with the warning..


    image

  • If you continue further on the wizard, you will get the prerequisites check failure messages


    image

Step 2: Installing DNS Server


  • In Server Manager –> click on Manage –> click Add Roles and Features Wizard –> click Next
  • Under Select installation type, select Role-based or feature-based installation –> click Next


    image

  • Under Select destination server –> click Next


    image

  • Under Select server roles –> click DNS Server
  • Under Add features that are required for DNS Server –> click Add Features –> click Next


    image

  • Click Next –> click Next –> Install


    image

  • Once the install the completed, let us configure DNS Server

Step 3: Configuring DNS Server


  • In Server Manager –> DNS
  • Under Servers –> right click WIN-DC –> click DNS Manager


    image

  • Under DNS Manager –> right click WIN-DC –> click Configure DNS Server…


    image

  • Under Configure a DNS Server Wizard –> click Next
  • Under Select Configuration Action –> click Create a forward lookup zone (recommended for small networks) –> click Next


    image

  • Under Primary Server Location –> click This server maintains the zone –> click Next

    NOTE: Since this is my Private Network, I selected This server maintains the zone else you could have selected ISP maintains the zone and followed the steps further

    image

  • Under Zone Name, type dotnetscraps.com –> click Next


    image

  • Under Zone File –> click Next


    image

  • Under Dynamic Update, I am going with the default Do not allow dynamic updates –> click Next


    image

  • Under Forwarders, I have selected No, it should not forward queries but you can select the first option as well –> click Next


    image

  • The wizard will search for Root Hints and return back –> click Finish


    image

  • This will give you the below error “Configure a DNS Server Wizard could not configure root hints” –> click OK


    image

  • In Server Manager –> DNS –> right click WIN-DC –> DNS Manager


    image

  • Expand WIN-DC –> Forward Lookup Zones, we can see dotnetscraps.com is now added in the Forward Lookup Zones


    image

  • Right click dotnetscraps.com –> click Properties


    image

  • Under General –> Dynamic update: select Nonsecure and secure –> click Apply


    image

Step 4: Configure DNSSEC (Optional, but you should configure DNSSEC in your domain)


  • In DNS Manager –> WIN-DC –> click Forward Lookup Zones –> right click dotnetscraps.com –> DNSSEC –> Sign the Zone


    image

  • I am going to use the default settings –> click Next


    image


    Click Next


    image


    Click Next


    image


    Click Finish


    image



Step 5: Promote the server to a domain controller


  • In Server Manager –> Notification –> click Promote this server to a domain controller
  • Under Deployment Configuration –> click Add a new forest –> type dotnetscraps.com –> click Next


    image

  • Under Domain Controller Options, type Directory Services Restore Mode *DSRM) password


    image

  • Under DNS Options –> click Change… –> click Next


    image

  • Under Additional Options –> type NetBIOS domain name: <I am leaving the default> –> click Next


    image

  • Under Paths –> change the Database, Log and SYSVOL folder paths –> click Next


    image

  • Under Review Options –> click Next
  • Under Prerequisites Check –> click Install


    image

  • The server is now configured as a domain controller


    image

Success !!

Hope this helps,
Vivek Kumbhar


Quote of the day:
People that are really very weird can get into sensitive positions and have a tremendous impact on history. - Dan Quayle


blog comments powered by Disqus

Rahul Soni

Rahul Soni  Twitter

 LinkedIn

 Facebook

 Email me



Vivek Kumbhar

Vivek Kumbhar  Twitter

 LinkedIn

 Facebook

 Email me


Stack Exchange

profile for Vivek at Server Fault, Q&A for system administrators and IT professionals

profile for Rahul Soni at Stack Overflow, Q&A for professional and enthusiast programmers

Calendar

<<  May 2013  >>
MoTuWeThFrSaSu
293012345
6789101112
13141516171819
20212223242526
272829303112
3456789

View posts in large calendar

All Items
Sign in

Visit Microsoft's Site

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.
© Copyright 2013, Rahul Soni

Powered by BlogEngine.NET 1.4.5.0