An old server may allocate addresses, resolve names and participate in domain logon at the same time. Before replacement, record dependencies rather than just its IP address. This guide inventories existing settings without changing zones, scopes or services.
1. Record roles and network context
Note server name, Windows 2000 edition, service pack, domain, IP addresses and subnets. Distinguish domain controller, member server and standalone server. Record which DNS, DHCP and, if applicable, WINS services are installed. An installed role and actual client use are separate evidence. Use authorized access and check existing backups first.
2. Read the DNS console
Open DNS through Administrative Tools and verify the selected server. Record forward and reverse zones, zone type, AD integration, primary or secondary role and visible server and zone settings. Note forwarders and important A, PTR, CNAME and SRV records with their purpose. Copying individual zone files does not automatically capture all DNS configuration; Microsoft identifies additional server settings requiring separate attention. Do not change zone types or dynamic updates for this inventory.
3. Document DHCP per scope
Open DHCP and record the server and existing authorization state without changing it. For each scope, record subnet mask, range, exclusions, reservations, lease duration and displayed activation state. Keep server, scope, class and reservation options separate. In particular map router, DNS servers and DNS domain name; server defaults do not prove every client’s effective settings. Do not delete leases or activate a second scope as an experiment.
4. Add client and application dependencies
Compare displayed IP, DNS and DHCP server details on selected existing clients with the table, without releasing or renewing addresses. Record static settings, router relay destinations and applications with fixed server names or addresses. Domain logon depends on internal DNS data including service location; opening an Internet website does not validate it. Do not substitute public resolvers as a quick fix.
5. Hand over checks and ownership
Use one row per dependency with source, consumer, setting, evidence date and responsible person. Mark unknowns explicitly. Plan separate replacement tests for name resolution, domain logon, address allocation and business applications, plus rollback. This inventory changes neither DNS nor DHCP and is not migration approval. Test copies must not issue production DHCP offers or communicate with the production domain.
