DNS (Domain Name System) is the service that translates human-readable names (like server1.company.local) into computer-readable IP addresses. Without DNS, we'd have to work with raw IP addresses everywhere. Let's walk through installing and configuring it on Windows Server, step by step.
Important note: if you've already installed AD DS...
If you've already installed Active Directory Domain Services, DNS Server is usually installed automatically alongside it (since AD fully depends on DNS). This tutorial is for anyone who wants to install and configure DNS separately and deliberately.
Step 1: Install the DNS role
From Server Manager, go to Add Roles and Features. Under Server Roles, check DNS Server and continue through to Install. Unlike many other services, DNS Server usually doesn't need extra post-deployment configuration and is ready to work right after installation.
Step 2: Create a Forward Lookup Zone
A zone is a "name book" that holds the records for a specific domain. From DNS Manager:
Right-click Forward Lookup Zones and select New Zone.
Choose Primary Zone as the zone type (the standard choice to start with).
Enter the zone name — e.g., company.local
Choose a Dynamic Update method based on your network's needs — Secure Only is usually recommended for Active Directory networks.
Step 3: Add DNS records
Now we need to add records that map a name to an IP. The most common type is an A record:
Right-click the zone you created and select New Host (A or AAAA).
Enter the host name (e.g., web1).
Enter the corresponding IP address (e.g., 192.168.1.50).
Click Add Host.
With this, any computer in this domain can reach 192.168.1.50 by typing web1.company.local.
Step 4: Configure forwarders
Your internal DNS server only knows names inside your organization's network — for users to also reach internet websites, you need to set up a forwarder:
Right-click the server name in DNS Manager and open Properties.
Go to the Forwarders tab and click Edit.
Add a valid public DNS server (e.g., 8.8.8.8).
With this setting, any request your internal DNS server can't answer gets automatically forwarded to that external server.
Step 5: Final test
From a client computer that has this server set as its DNS, run:
nslookup web1.company.local
If the correct IP address is returned, everything's working correctly.
DNS is one of those services that nobody notices when it's working right, but when it breaks, the entire network grinds to a halt — which is exactly why mastering it, just like what's taught in my MCSA courses, is essential.
Blog