> For the complete documentation index, see [llms.txt](https://ajmal-anwar.gitbook.io/zyberspace-by-ajmal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ajmal-anwar.gitbook.io/zyberspace-by-ajmal/zyberlab/02-active-directory-basics/configure-static-ip-dc01.md).

# Configure a Static IP Address on DC01

## Objective

Give `DC01` a stable IPv4 address before installing Active Directory.

A domain controller should not depend on an address that may change unexpectedly because domain members and DNS need to find it reliably.

## Before You Begin

On `DC01`, open Command Prompt and run:

```
ipconfig /all
```

Record the current:

* IPv4 address
* subnet mask
* default gateway
* DNS server

Do not copy an address from this guide blindly. Use the actual VMware NAT network shown on your system.

## Example Only

If your VMware NAT network were `192.168.100.0/24`, a simple lab configuration could look like:

```
DC01 IPv4:       192.168.100.10
Subnet mask:     255.255.255.0
Default gateway: 192.168.100.2
DNS server:      192.168.100.10
```

Your values may be different.

Choose an address that belongs to the correct VMware subnet and does not conflict with another device or the VMware DHCP pool.

## Configure the Address Manually

1. Open **Control Panel**.
2. Go to **Network and Internet** → **Network and Sharing Center**.
3. Select **Change adapter settings**.
4. Right-click the active Ethernet adapter and select **Properties**.
5. Select **Internet Protocol Version 4 (TCP/IPv4)**.
6. Select **Properties**.
7. Choose **Use the following IP address**.
8. Enter the IPv4 address, subnet mask, and default gateway you recorded or selected for the lab.
9. Set **Preferred DNS server** to the same IPv4 address assigned to `DC01`.
10. Select **OK** and close the remaining windows.

## Why Does DC01 Point DNS to Itself?

After Active Directory is installed, `DC01` will also provide DNS for the lab domain.

Active Directory creates DNS records that allow clients to locate services such as domain controllers. Pointing the domain controller to its own DNS service keeps domain name resolution inside the lab environment.

## Verify

Run:

```
ipconfig /all
```

Confirm the new address is shown.

Then test the default gateway:

```
ping <default-gateway>
```

If internet access is expected through VMware NAT, you can also test name resolution:

```
nslookup example.com
```

Before DNS is installed on `DC01`, external name resolution may not work when the DNS address points to itself. That is expected at this stage and will be corrected after the DNS role becomes active and forwarding is available.

## Security Relevance

A stable domain controller address reduces configuration errors and makes DNS, authentication, logging, and later monitoring exercises predictable.

## Checkpoint

Do not continue until you know the final IPv4 address of `DC01`. You will need it when configuring `CLIENT01` for the domain.
