# Static IP & DNS Configuration ### Overview Before the Domain Controller promotion could complete, the Windows Server 2019 VM required a static IP address and proper DNS configuration. This is not optional — it is a fundamental requirement for any Domain Controller in any environment, lab or production. *** ### Why a Domain Controller Must Have a Static IP A Domain Controller is the most critical server on any Active Directory network. Every device on the domain depends on it for: * Authentication (logging in) * DNS resolution (finding resources) * Group Policy delivery * Kerberos ticketing If the DC's IP address changes — as it would with DHCP — none of these services can be reliably reached. Client machines would lose the ability to log in, find resources, or receive policy updates. > **MSP Context:** When an MSP technician sets up or inherits a client environment, one of the first things verified is that all Domain Controllers have static IPs that are properly documented. A DC running on DHCP is considered a critical misconfiguration. *** ### The Problem Encountered When the VM was first created, Hyper-V assigned it a dynamic IP via DHCP. Running ipconfig /all revealed: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://stefs-documentation.gitbook.io/stefs-documentation-docs/project-overview-bare-metal-homelab/active-directory/static-ip-and-dns-configuration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.