Windows Server 2025 / How to Install DNS and Create Zones and Records

Install the DNS role, create a primary zone, and add a host record to practice internal name resolution on Windows Server 2025. This lab uses lab.example.test on DC1 before domain promotion, keeping it separate from the future AD zone.

Check existing data and the lab network

DC1 uses 172.24.50.10/24 and FS1 uses 172.24.50.20/24. Both and CLIENT1 belong to the same isolated network. Never overwrite an existing operational zone or record for a practice exercise.

• Verify DC1’s static address and administrator access.
• Reserve lab.example.test for practice and ad.example.test for the domain.
• Verify FS1’s actual address and avoid duplicate names with conflicting values.
• External resolution is unnecessary for this internal lookup exercise.

Install DNS and the supported tools

Run on DC1 in elevated Windows PowerShell and review success and restart requirements:

Install-WindowsFeature -Name DNS -IncludeManagementTools
Get-WindowsFeature -Name DNS
Get-Service -Name DNS

Alternatively use Server Manager → Add Roles and Features → DNS Server. Follow Microsoft’s DNS setup guide. Check that DNS is running and DNS Manager, dnsmgmt.msc, is connected to DC1. Manage Core through PowerShell or remote DNS Manager.

Create the practice primary zone and host

1. In DNS Manager on DC1, right-click Forward Lookup Zones and select New Zone.
2. Choose a primary zone; do not assume AD-integrated storage is available before AD exists.
3. Use lab.example.test and create a file-backed zone.
4. Disallow dynamic updates for this practice zone. Domain secure updates are a later configuration.
5. Create a New Host record named fs1 with address 172.24.50.20.

The following is an alternative for an environment without that zone. Do not execute both creation methods. Review DNS zone management for the storage options.

Add-DnsServerPrimaryZone -Name 'lab.example.test' -ZoneFile 'lab.example.test.dns' -DynamicUpdate None
Add-DnsServerResourceRecordA -ZoneName 'lab.example.test' -Name 'fs1' -IPv4Address 172.24.50.20
Get-DnsServerResourceRecord -ZoneName 'lab.example.test' -Name 'fs1'

Add a reverse zone and alias

Under Reverse Lookup Zones, create an IPv4 /24 zone for network ID 172.24.50. Its reverse name is 50.24.172.in-addr.arpa. Confirm that the range matches the lab.

1. Create a PTR for address suffix 20 pointing to fs1.lab.example.test.
2. In the forward zone, create CNAME portal targeting fs1.lab.example.test.
3. Inspect the A, alias, and PTR values separately.

The alias demonstrates DNS resolution, not completed web or file-share access. Automatic PTR creation also requires a suitable reverse zone; verify the result rather than relying on the checkbox.

Verify three lookups from the client

CLIENT1 can query DC1 explicitly before changing its default resolver:

Resolve-DnsName 'fs1.lab.example.test' -Type A -Server 172.24.50.10
Resolve-DnsName 'portal.lab.example.test' -Type CNAME -Server 172.24.50.10
Resolve-DnsName '172.24.50.20' -Type PTR -Server 172.24.50.10

Expect A to return 172.24.50.20, CNAME to identify fs1.lab.example.test, and PTR to return the host name. For timeouts, inspect service and connectivity. For name errors, inspect spelling, zone, and record type. DNS uses UDP and TCP 53, so a TCP test alone does not prove every query path.

To compare a reversible change, remove only the practice portal alias, observe failure, recreate it, and observe success. Do not repeat that deletion exercise on AD service records. Keep or remove the practice zone separately after checking its dependencies.