# DHCP Configuration

## DHCP Server
- Server Name: ISP Router
- Server IP: 10.0.0.1
- Failover Partner: None

**Note:** The Windows Server DHCP role is installed on SERVER (10.0.0.5) but has **zero scopes configured**. All DHCP is handled by the ISP router.

## Scopes

### Scope - LAN (ISP Router)
- Subnet: 10.0.0.0/24
- Range Start: Unknown — need to check ISP router admin interface
- Range End: Unknown
- Subnet Mask: 255.255.255.0
- Default Gateway: 10.0.0.1
- DNS Servers: **Unknown — critical to verify** (should be 10.0.0.5 for AD)
- Lease Duration: Unknown

## Reservations

No reservations documented. Need to check ISP router for any existing DHCP reservations.

| Device Name | MAC Address | IP Address | Scope | Notes |
|------------|-------------|------------|-------|-------|
| SERVER | — | 10.0.0.5 | LAN | DC — should be reserved or static |
| UniFi Switch | 0C:EA:14:8A:8D:7F | 10.0.0.122 | LAN | Should be reserved |

## DHCP Relay
- Not applicable — single subnet, DHCP server on same segment

## Issues
1. **DHCP on ISP router instead of server** — Less control over DHCP options (DNS, NTP, lease times). Cannot manage reservations centrally via Windows tools. ISP router may hand out ISP DNS instead of the DC's DNS (10.0.0.5), which would break AD name resolution.
2. **Windows DHCP role installed but unused** — Creates confusion. Either uninstall or migrate DHCP to the server.

## Recommendations
1. **Migrate DHCP to Windows Server** — Provides centralized management, AD-integrated DNS updates, DHCP reservations via PowerShell, and logging.
2. **Create reservations** for: SERVER (10.0.0.5), UniFi switch (10.0.0.122), printers, and any other infrastructure.
3. **Set DNS option** — Ensure DHCP hands out 10.0.0.5 as the primary DNS server.

## TODO
- [ ] Log into ISP router and document DHCP scope, range, DNS settings, and any reservations
- [ ] Verify what DNS servers DHCP clients receive
- [ ] Plan DHCP migration from ISP router to Windows Server
- [ ] Create DHCP reservations for infrastructure devices
