About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
New laptops and phones get a 169.254 address or no network at all, and existing devices fail as their leases run out. The DHCP server is running, the scopes are there, but the server has decided it is not allowed to hand out addresses.
In an Active Directory domain, a Windows DHCP server must be on the domain's list of authorised DHCP servers before it leases addresses. Microsoft describes the automatic disabling of unauthorised servers as a security feature that stops a stray DHCP server handing out wrong addresses (Microsoft Learn, Install and configure DHCP Server).
What you see
Microsoft lists these symptoms (Microsoft Learn, Troubleshooting guide: DHCP authorization failures):
- After installing the role: Authorizing DHCP server ….. Failed, with Error Code: 20070. The DHCP service could not contact Active Directory.
- A red down arrow on IPv4 in the DHCP console.
- Event ID 1046 in the System log: the DHCP/BINL service "has determined that it is not authorized to start. It has stopped servicing clients."
- Manual authorisation failing with The specified domain either does not exist or could be contacted.
A pattern worth recognising: authorisation works when done by hand, then fails again days later.
Why it happens
Authorising a server creates an entry for it in Active Directory's Configuration partition, under Services > NetServices. Microsoft states the DHCP server checks its status there every hour over LDAP, and if its IP address is not in the list, it deauthorises itself.
Microsoft's listed causes:
- Permissions. The account used to authorise the server does not have enough rights.
- Missing entry. The server's entry was deleted from the Configuration container.
- Connectivity. Network or firewall problems block LDAP between the DHCP server and the domain controller.
- Replication problems. Delays or faults can leave duplicate or conflicting entries (CNF objects) that stop the server being authorised.
Because the hourly check looks for the server's IP address, a server whose address has changed since it was authorised can drop off the list even though an entry with its name still exists. (This follows from Microsoft's description of the check; it is not one of the causes Microsoft lists.)
How to prove the cause
1. List the authorised servers (troubleshooting guide):
Get-DhcpServerInDC
or from a command prompt:
netsh dhcp show server
Check that the server is listed, with its current name and IP address.
2. Look in ADSI Edit. On a domain controller run adsiedit.msc, connect to the Configuration container and go to Configuration > Services > NetServices. Look for the server's name, and for any entry with a CNF tag in its CN, for example cn <fqdn>CNF:ca69f501234.
3. Test connectivity to the domain controller from the DHCP server:
Test-NetConnection -ComputerName <DC-IP> -Port 389
Microsoft says LDAP (TCP and UDP 389) must be open between them, and suggests a packet capture if packets are being dropped.
4. Check the account. Microsoft's guide uses an Enterprise Admin account to authorise.
5. If the entry keeps disappearing, turn on auditing to find out who or what deletes it (see "What to watch afterwards").
The fix
Authorise the server with an Enterprise Admin account: in the DHCP console, right-click the server name and select Authorize, then refresh. Microsoft notes it can take a few seconds, and a green icon should appear on each scope. In PowerShell (Microsoft Learn, Add-DhcpServerInDC):
Add-DhcpServerInDC -DnsName <server FQDN> -IPAddress <server IP>Microsoft's reference notes this also tells the DHCP service to run an authorisation check straight away, even when the entry already exists.
Remove a CNF entry. Microsoft recommends taking an Active Directory backup first, then deleting the conflicting object in ADSI Edit, then authorising the server again.
Replace an entry with an old address. Remove the stale entry with its old name and address (Microsoft Learn, Remove-DhcpServerInDC), then authorise with the current ones. Microsoft says the remove command also "triggers the DHCP server service to perform an authorization check", even if the removal fails, so a running server can stop leasing until it is authorised again. Run both commands together, in a quiet period:
Remove-DhcpServerInDC -DnsName <old FQDN> -IPAddress <old IP>Open LDAP (TCP/UDP 389) between the DHCP server and the domain controllers if a firewall blocks it.
Fix replication if domain controllers disagree, so the authorised list is the same everywhere.
How to confirm the fix
Get-DhcpServerInDClists the server with its current name and IP address.- The DHCP console shows IPv4 without the red arrow, and the scopes show green.
- No new event 1046 appears after the next hourly check, and new devices receive addresses from the expected scope.
What to watch afterwards
- An entry that vanishes again. Microsoft's guide shows how to audit it: in the Default Domain Controllers Policy, enable Audit Directory Service Changes (Success and Failure) under Advanced Audit Policy Configuration > DS Access. Then in ADSI Edit, on Services > NetServices, add an auditing entry for Everyone with Write All Properties, Delete and Delete Subtree. When it happens again, the domain controller's Security log shows "A directory service object was deleted" with the account that did it.
- Server moves, renames and readdressing. Each one is a moment to check the authorised list.
- Event 1046 in the DHCP server's System log; worth an alert.
Read next
Related articles you may want next.
- HostingWindows DHCP Failover: Partner Down, Lease Conflicts and RecoveryWindows DHCP failover stuck in communication interrupted, partner down or recovering from an old copy? Read the state, understand MCLT, then recover without duplicate leases.Read article
- Backup & RecoveryDHCP, the address plan, and DNS: which record you restore firstWhy Kea lease files, subnet configuration and DNS updates have to be restored in a chosen order. RFC 2131 persistent storage and Kea 3.2.1.Read article
- TroubleshootingDHCP scope full: clients get 169.254 addresses. Find what took the leasesNew devices get a 169.254 address while older ones keep working. Check the scope's usage, find declined (BAD_ADDRESS) leases and unexcluded static addresses, and fix the range, lease time or failover split on a Windows DHCP server.Read article
Risks and limits
- Deleting objects in the Configuration partition affects the whole forest. Take an Active Directory backup first, as Microsoft advises, and delete only the specific CNF or stale entry.
- Removing the authorisation of a server that is still in use stops it leasing addresses. Confirm the name and IP address before running
Remove-DhcpServerInDC. - The auditing settings add Security log volume on domain controllers; set the log size to match.
- This covers authorisation only. A server that is authorised but whose scope is full or whose failover partner is down is a different fault.
Sources
- Microsoft Learn, "Troubleshooting guide: DHCP authorization failures", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshooting-guide-dhcp-authorization-failures
- Microsoft Learn, "Quickstart: Install and configure DHCP Server", applies to Windows Server 2016–2025, last updated 21 April 2025: https://learn.microsoft.com/en-us/windows-server/networking/technologies/dhcp/quickstart-install-configure-dhcp-server
- Microsoft Learn, "Add-DhcpServerInDC" (DhcpServer module reference), dated 20 December 2016: https://learn.microsoft.com/en-us/powershell/module/dhcpserver/add-dhcpserverindc
- Microsoft Learn, "Remove-DhcpServerInDC" (DhcpServer module reference), dated 20 December 2016: https://learn.microsoft.com/en-us/powershell/module/dhcpserver/remove-dhcpserverindc
Next step
A DHCP server that keeps losing its authorisation needs the cause found, not only the authorise button pressed again. NetLeverage has looked after business servers since 2002. If devices are not getting addresses, talk to us through managed support with the Get-DhcpServerInDC output and the latest event 1046.
This article was originally published on .