Windows Server / DNS, DHCP & Server Networking
Check which interfaces a Windows DHCP server listens on
A multihomed server can be healthy while DHCP is bound to the wrong interface. Inspect bindings before changing routing or scopes.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-DhcpServerv4Binding -ComputerName DHCP01Read the result
The command reports configured IPv4 DHCP interface bindings. It does not prove that client broadcasts or relay traffic reach the interface.
Resolve and verify
Compare enabled bindings with the approved server VLAN and relay design. Correct the intended binding through the DHCP owner and test one client on the affected subnet.
Before changing production
Do not enable DHCP on management or public interfaces without an explicit network design decision.