Windows Server 2025 Static IP and Server Name Set Them Before Any Role
Two ten-minute jobs — a fixed IP address and a proper name — decide how smooth the next five years are. Do them before any role exists, and never treat a domain controller rename as a casual right-click afterwards.
✍️ Technical Anshu🪟 Windows Server 2025⏱️ Identity setup guide
🎥 Watch the complete Server 2025 setup in the video — install, roles and hardening, step by step
Every service on a network points at the server by address and by name. Clients ask it for DNS answers, logins and files using values that get configured once and then assumed forever. That is why the server's identity is fixed first, before roles: a static IP that cannot drift, and a name chosen like it will be spoken on the phone during an emergency — because it will be.
The identity card of a healthy first server. Address values are examples — use your own LAN range.
1
Why a Server Never Takes Its Own Address From DHCP
DHCP is a wonderful service — for clients. For the server itself it is a trap. If the server's address changes at a lease renewal, every pointer in the office breaks at once: DNS records, mapped drives, printer ports, firewall rules, backup jobs. Nothing announces the change; things simply stop working on a random Tuesday.
Give the server a static address inside the LAN subnet
Pick it outside the DHCP scope — if DHCP hands out .100 to .200, the server at .10 can never collide with a client
Write the address in the handover document and on a label on the machine itself
2
Set the Static IP Step by Step
On Desktop Experience: open the network adapter's properties, choose Internet Protocol Version 4, and enter the address, mask and gateway manually. On Server Core, the same job is option 8 in sconfig. For DNS, there is a timing detail that confuses everyone once:
Before promotion, the server can point DNS at the router or a public resolver so updates work — for example the gateway 192.168.1.1
After promotion to a domain controller, its DNS must point at itself — 127.0.0.1 or its own address — because it now hosts the domain's DNS zone
Outside queries are then handled by forwarders in the DNS console, which pass internet names to your ISP or a public resolver
Verify with ipconfig /all and a quick nslookup of your domain name before moving on
3
Name the Server Like It Will Be Read Aloud in a Panic
The computer name is set in the same session, while renaming is still free. Keep it short, boring and descriptive: a pattern like SRV-DC01 (server, role, number) tells any technician what the machine is before they log in. Avoid spaces, avoid cute names, and avoid the owner's name — servers outlive org charts.
System Properties → Change → type the new name → restart when asked
Or in PowerShell: Rename-Computer -NewName 'SRV-DC01' -Restart
Do this now. Five minutes after installation, a rename costs one restart. Five months after promotion, it costs a project
4
The Renaming Truth — Why a Domain Controller Is Different
An ordinary member server can be renamed with mild care. A domain controller cannot be casually renamed, because its name is woven into Active Directory replication, DNS records, certificates and the Kerberos tickets every login depends on. There is a documented netdom procedure that adds an alternate name, promotes it and removes the old one — it exists, and experienced admins still treat it as surgery, not housekeeping.
If the DC's name is merely ugly — leave it. Ugly works perfectly
If the name is genuinely wrong (wrong site, wrong role), the safe office route is to build a second DC with the right name, move the roles, and retire the old one
Whatever you do, never rename a DC the evening before a working day and hope replication forgives you
🔴 Remember the order: static IP and final name come before Active Directory, never after. Ten careful minutes here remove an entire category of "the server disappeared" and "logins broke" mysteries from your future.
🎥 Watch the Identity Setup in the Video
See the static IP, name and time zone being set on the fresh Server 2025 install, exactly in this order.
Any free address inside your LAN subnet that sits outside the DHCP scope. A common pattern: router at 192.168.1.1, server at 192.168.1.10, DHCP handing clients 192.168.1.100 onwards. The exact numbers matter less than the discipline — fixed, documented and collision-free.
Why does the domain controller point DNS at itself?
Because after promotion, it is the DNS server for the domain. It must ask itself for domain records, and it forwards everything else to the internet through the forwarders you configure in the DNS console. Pointing a DC at a public DNS instead is a classic cause of slow logins and missing domain records.
Can I rename a domain controller later if I must?
Technically yes — a documented netdom procedure exists. Practically, treat it as surgery with replication-wide side effects. The safer office answer is to promote a second domain controller with the correct name, transfer the roles, and demote the old one.
This guide is based on Technical Anshu's Windows Server 2025 complete setup video • Stuck on any step? Ask in the video comments — you will get help there 🙏