Setting up a windows domain

This example uses Windows Server 2025

Here we will set up Active Directory Domain Services (AD DS) and DNS on a fresh Windows Server 2025 instance for the dalzell.remote domain.

Phase 1: Configure Static Network Settings

The server must have a static IP address and point to itself for DNS resolution.

1). Change your network settings to (working example);

IP address: 10.29.15.103

Subnet mask: 255.255.255.0

Default gateway: 10.29.15.1

Select Use the following DNS server addresses:

Preferred DNS server: 127.0.0.1 (or 10.29.15.103)

Click OK, then OK again.

2). Rename the computer to something recognizable, in this case DALZELL-AD01 via System Properties (sysdm.cpl) and restart the server.

Phase 2: Install AD DS Role

1). Open Server Manager.

2). Select Add Roles and Features.

3). Check the box for Active Directory Domain Services and I think I also chose DNS Server.

4). Ensure Include management tools is selected.

5). On the next screen, the following was checked;

.Net Framework 4.8

WFC Service > TCP Port Sharing.

Group Policy Management.

Microsoft Defender Antivirus

Remote Server Management > Role Admin Tools > AD DS Tools > Active Directory Admin and AD DS Snap In Tools.

Remote Server Management > Role Admin Tools > DNS Server Tools.

SMB 1.0 (for older windows clients)

System Data Archiver.

Windows Admin Center.

Windows Powershell > 5.1

Wireless Lan Service

WoW 64 support.

XPS Viewer.

6). You may need to reboot once complete.

Phase 3: Promote Server to a Domain Controller

Some of the steps here may not be correct, most were from memory and retrospective Google Fu.

1). Promote this server to a domain controller.

2).  Add a new forest.

3). Enter the Root domain name: dalzell.remote

4). In Domain Controller Options:

Leave Forest functional level and Domain functional level set to Windows Server 2025 (or highest available).

Ensure Domain Name System (DNS) server and Global Catalog (GC) are checked.

Type a secure Directory Services Restore Mode (DSRM) password and confirm it.

5). Click Next through DNS Options (ignore the delegation warning, as this is a new root zone).

6). Verify the NetBIOS domain name automatically populates as DALZELL (or DALZ), then click Next. (I'm not so sure this actually happened).

Leave default database, log, and SYSVOL paths, and click Next.

Review the summary screen and click Next.

The setup wizard will perform prerequisite checks. Once you see the green checkmark stating All prerequisite checks passed successfully, click Install.

7). Restart-Service Netlogon, DNS

ipconfig /registerdns

Phase 4: Post-Install Verification

1). Once the server reboots, log in using the domain administrator account (DALZELL\Administrator).

2). Run the following:

Restart-Service Netlogon, DNS

ipconfig /registerdns 

3). Verify DNS SRV Records, Open PowerShell as Administrator and run;

Resolve-DnsName -Name _ldap._tcp.dc._msdcs.dalzell.remote -Type SRV -Server 127.0.0.1

We should see something like:

QueryType : SRV
NameTarget : DALZELL-AD01.dalzell.remote
Port : 389
IP4Address : 10.29.15.103

4). Verify Active Director Services;

Get-Service -Name NTDS, DNS, Netlogon | Select-Object Name, Status

5). Run the AD diagnostic tool;

dcdiag /test:dns /v

We should see something like;

Connectivity: PASS
Advertising: PASS
RegisterInDNS: PASS

6). Verify AD Services;

Get-Service -Name NTDS, DNS, Netlogon, KDC | Select-Object Name, Status

NTDS, DNS, Netlogon and KDC services should show running.

7). Test UDP/TCP Port 53 Listening State;

Get-NetTCPConnection -LocalPort 53

We should see LocalAddress: 10.29.15.103 (or maybe 127.0.0.1) with State: Listen