Before promoting your server to a domain controller, configure DNS and DHCP. DNS enables name resolution and domain location; DHCP automates IP and DNS distribution to clients.
Windows Server Roles
Windows Server Roles are predefined feature sets that let a server deliver specific network services and infrastructure functions.
Active Directory Domain Services (AD DS) — makes the server a domain controller.
DNS Server — handles name resolution inside the network.
DHCP Server — assigns IP addresses and network options to clients.
File and Storage Services — hosts and manages file shares and storage.
In a lab, assigning and configuring these roles simulates real-world IT infrastructure for hands-on learning in domain management, policy enforcement, and network services—right from your VirtualBox Windows Server.
Overview
Before setting up Active Directory, configure two critical services: DNS and DHCP.
DNS resolves domain names to IP addresses and allows clients to locate domain controllers.
DHCP automatically assigns IP addresses and options like gateway and DNS servers.
This lab configures both on the same Windows Server that will later function as a domain controller.
Without DNS
You cannot promote the server to a domain controller.
Clients will not be able to join the domain.
Without DHCP
Every client would need manual IP configuration—inefficient and error-prone.
Configuring Internal DNS (Windows Server 2016)
Verify DNS Installation
In this example the DNS Server role is already installed—so we’ll verify.
Open DNS Manager (dnsmgmt.msc)
Confirm a Forward Lookup Zone exists for your domain (e.g., Domain-1.local)
Zone contains A records used for domain authentication
Configure DNS Forwarders (Optional)
Forwarders allow internal DNS to resolve external names via public DNS servers.
Right-click your server in DNS Manager → Properties
Go to the Forwarders tab
Add:
8.8.8.8 (Google DNS) · 1.1.1.1 (Cloudflare DNS)
Click OK to save
Configuring DHCP
Install the DHCP Server Role
1) Click Add roles and features in Server Manager
2) Follow the wizard prompts
3) Choose Role-based or feature-based installation
2) Click Complete DHCP configuration to open the wizard and authorize the server
3) Specify credentials to authorize in AD DS → Commit
In this example, I select a specified user’s credentials and commit the changes.
Create a DHCP Scope
1) Server Manager → Tools → DHCP
2) DHCP Manager
3) Expand the server/domain hierarchy
4) Right-click IPv4 → New Scope…
5) New Scope Wizard
6) Name the scope (e.g., Lab Scope)
7) Configure IP address range
Start IP Address
End IP Address
CIDR length / Subnet mask
8) Exclusions (optional)
9) Lease Duration
10) Configure DHCP Options
11) Default Gateway (e.g., 192.168.1.1)
12) Domain Name & DNS Servers (use your internal domain and DNS)
13) WINS (if applicable)
14) Activate the scope
15) Finish
16) Verify the new scope under IPv4
This walkthrough configured internal DNS and DHCP on Windows Server 2016—the two key services to set before promoting to a domain controller. Next up: installing the AD DS role and standing up Active Directory.