Windows Server’s DNS role can host zones and resolve queries for a network. This guide installs the role and configures its listening addresses and optional forwarders on a supported Windows Server.
Before you begin
Use a static IP address and an administrative account. Decide whether the server is an internal resolver, an authoritative server or part of Active Directory. Domain-controller DNS needs an AD-aware design rather than an arbitrary standalone setup.
Back up existing settings before changing an established DNS server. Restrict access to the clients that should use recursive resolution; do not expose an unrestricted public resolver.
Install the DNS role
In administrative Windows PowerShell:
Install-WindowsFeature -Name DNS -IncludeManagementToolsCheck the installation result and any restart requirement reported by Windows.
Set listening interfaces
Identify the intended static IP using Get-NetIPAddress. Record the current configuration, then replace the example address below with the server’s actual address:
$DnsSettings = Get-DnsServerSetting -All
$DnsSettings.ListeningIpAddress = @('192.0.2.10')
Set-DnsServerSetting -InputObject $DnsSettingsThe example address is a documentation placeholder. Limiting listening interfaces does not itself configure firewall or recursion access controls.
Configure resolution
New installations provide root hints. Inspect them with:
Get-DnsServerRootHintNormally retain these rather than replacing a root-server address with an arbitrary IP.
If your network uses approved upstream resolvers, record the current forwarders and set their actual addresses:
Get-DnsServerForwarder
Set-DnsServerForwarder -IPAddress '192.0.2.53','198.51.100.53'Replace both placeholders. This changes the configured forwarder list, so retain any required existing entries.
Configure zones and test
In DNS Manager, review or create the appropriate forward lookup zone and records for the intended namespace. Choose storage, update permissions and replication to fit the server’s role; do not create a duplicate AD zone without checking the existing design.
Test a known record against this server with Resolve-DnsName -Name example.com -Server SERVER_IP, replacing the hostname and address. Hosting a public zone also needs the correct delegation and network access; installing the role alone does not change public DNS.