Windows Server 2025 / How to Set the Computer Name, Static IP, DNS, and Time

After installing Windows Server 2025, configure its name, static IP, DNS, and time before adding services. Domain members need internal DNS that can locate domain controllers; make potentially disruptive IP changes from the console.

Record the address plan and original settings

The isolated example subnet is 172.24.50.0/24: DC1 uses .10, DC2 .11, and FS1 .20. Check for overlap with the host network, VPN, and other virtual networks before using these examples.

hostname
Get-NetAdapter
Get-NetIPConfiguration
Get-DnsClientServerAddress -AddressFamily IPv4
Get-TimeZone

Record adapter names and indexes, addresses, prefix lengths, gateways, DNS servers, and time zone. With several adapters, identify the one connected to the lab switch. Do not change a remotely managed address until you have a VM console or another recovery route.

Set the computer name first

In Desktop Experience, open Server Manager → Local Server → Computer name. In Core, use SConfig. To name a new member server FS1, run the following in elevated Windows PowerShell:

Rename-Computer -NewName 'FS1'
Restart-Computer

Restart-Computer restarts immediately, so save work first. After signing in, use hostname to verify the change. Set a domain controller’s final name before promotion; do not apply this simple rename example to an already promoted controller.

Configure static IPv4 on the isolated network

1. Open ncpa.cpl, identify the intended adapter, and open its properties.
2. Open Internet Protocol Version 4 properties. For FS1, enter 172.24.50.20 and subnet mask 255.255.255.0.
3. Leave the gateway empty when communication stays within a network without a router. For external access, use the actual configured router or NAT address.
4. Set DNS according to the deployment stage below, apply changes, and verify with Get-NetIPConfiguration.

For PowerShell configuration, review New-NetIPAddress requirements. Adding or removing addresses and routes without checking their current state can disconnect the server. This lab changes settings individually through the GUI or SConfig.

A failed ping does not prove that an address is unused: another device may block Internet Control Message Protocol (ICMP) replies. Check the network’s address allocation records when investigating conflicts.

Choose DNS for the current deployment stage

Public resolvers cannot locate the controllers of ad.example.test. If clients need external names, configure forwarding and connectivity on internal DNS rather than adding public resolvers to domain clients. A resolver address is useful only when a DNS service actually responds there.

Separate time zone from time synchronization

For a lab using Korean local time, the following example sets the corresponding time zone. Choose your actual time zone elsewhere. Matching zones does not guarantee that clocks show the same real time.

Set-TimeZone -Id 'Korea Standard Time'
Get-Date
w32tm /query /status
w32tm /query /source

Standalone servers and domain members have different synchronization arrangements. Windows Time service documentation explains the domain hierarchy. Do not independently force a different external time source onto every domain member.

Record final names, IPs, DNS settings, and time sources. If access fails, use the console to compare original values and restore incorrect addresses, masks, or gateways. After fixing DNS, repeat the same query against the same server to make the comparison meaningful.