How to Install and Configure AD DS and DNS in Windows Server 2016


This guide shows how to install AD DS and DNS step by step, with every setting in the order you will use it. Active Directory Domain Services (AD DS) and DNS are installed together so often that it is worth seeing the whole combined flow in one place. AD stores users, computers and policies; DNS is how clients find the domain at all. This guide installs both on one Windows Server 2016 machine — the classic first lab server.

install AD DS and DNS in a home lab

WINDOWS SERVERINSTALL AD DS AND DNSENTERPRISE LABtimer 45 MIN LAB
NH
Nurul Huda AUTHORInfrastructure & Cloud Architect · Verified 2026

print Print Lab

● VALID ON THE CONFIG BELOW

dns LAB TOPOLOGY & PREREQUISITES

# example values used while writing and testing this guide

LAB VM

HypervisorESXi / Workstation
vCPU2
RAM4-8 GB
Disk60 GB thin

WINDOWS BUILD

EditionServer 2019 Std
InterfaceDesktop Experience
Adminlocal Administrator
IPstatic or DHCP

VALIDATION

RolesServer Manager
Firewalllab rules only
Snapshotbefore changes

01constructionInstall AD DS and DNS: Prerequisites

  • Windows Server 2016 VM installed (see the VM installation guide) with a static IP
  • Set the NIC’s DNS server to the machine’s own IP — a common and confusing mistake is leaving DHCP DNS here
  • Decide the domain name, for example lab.local

02downloadStep 1: Install Both Roles at Once

Server Manager → Add Roles and Features → select Active Directory Domain Services; the wizard adds the required features and, if you want, add DNS Server in the same pass (the AD promotion will do it for you anyway). In PowerShell:

Install-WindowsFeature AD-Domain-Services,DNS -IncludeManagementTools In short, to install AD DS and DNS reliably, follow the order above and verify each step.

03usbStep 2: Promote to a Domain Controller

Click the flag warning → Promote this server to a domain controller:

  1. Deployment configuration: Add a new forest with your root domain name
  2. DC options: functional levels + DNS server checked; set the DSRM password
  3. Ignore the DNS delegation warning (normal without internet-facing DNS rights)
  4. Review and install; the server reboots as the DC and DNS server

04terminalStep 3: Verify AD and DNS Together

  • DNS Manager shows the lab.local zone with SRV records — proof AD published itself correctly
  • nslookup lab.local from a client (after setting its DNS to the DC) resolves
  • Active Directory Users and Computers opens your domain
  • Join a second VM to the domain to test the full chain: DNS → DC → authentication

05settings_ethernetDeeper Dives

Each piece deserves its own practice: the standalone domain controller walkthrough, the dedicated DNS server guide with zones and records, plus DHCP so clients get the DC’s address automatically. In short, to install AD DS and DNS reliably, follow the order above and verify each step.

Related Content

▶ UP NEXT IN THE WINDOWS TRACK

How to Create a Domain Controller in Windows Server 2016/2019

Finish this lab, then continue down the track. Each guide builds on the one before it.

rocket_launch Launch Next Lab