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.
Event 1056 is a warning from the DhcpServer source. Microsoft's event page is written for Windows Server 2003, and the remedy is shown for later releases only through the PowerShell cmdlet pages. The event says the DHCP Server service found it is running on a domain controller with no credentials configured for the Dynamic DNS registrations it makes for clients, and that this is not a recommended security configuration. The fix is to give the DHCP server a credential: a dedicated, non-expiring user account that it uses for those DNS updates.
The credential is not the same thing as the DnsUpdateProxy group. Microsoft describes them as separate mechanisms, and says the group on its own leaves DHCP-registered records unsecured.
What the error means
Microsoft's event 1056 page gives the text: "The DHCP service has detected that it's running on a domain controller and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. This isn't a recommended security configuration." It adds that credentials can be set with the command line netsh dhcp server set dnscredentials or in the DHCP administrative tool.
The reason is in the page's "More information" section. The DHCP Server service runs under the domain controller's computer account and so has full control of all DNS objects. DNS records it registers dynamically can then have their name records overwritten by an earlier version of the DHCP client, which Microsoft says is undesirable, especially when the zone allows secure updates only. With the DNSCredentials setting, the service performs DNS updates as a specified account that cannot overwrite those records. Microsoft "strongly recommends" using it when DHCP and DNS run on the same domain controller, and says that without it you should run the services on different computers.
Scope matters. The event 1056 page is labelled "Applies to: Windows Server 2003", and its symptom is a domain controller that also runs DNS. The DnsUpdateProxy page is archived and written for Windows Server 2008. Neither page describes later releases beyond the PowerShell cmdlets, whose pages cover Windows Server 2016 to 2025. The cmdlet pages show that a DHCP server can be given an account for DNS registrations on those releases.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| DHCP Server role installed on a domain controller with no credentials set | Warning 1056 in the System log, source DhcpServer | Get-DhcpServerDnsCredential shows no user name (the page does not show output for an unset credential) |
| A second DHCP server on a domain controller (for example a failover partner) was never given the credential | Event 1056 on that server only | Run Get-DhcpServerDnsCredential against each DHCP server in turn |
| DHCP is relied on to register records and the zone is secure-only | DHCP-created records are missing or cannot be updated by another server | Zone settings allow only secure dynamic updates; Microsoft's page says secure updates might fail if credentials are not configured |
| DnsUpdateProxy used instead of credentials | Records registered by the DHCP server are not secured | The DHCP server or domain controller is a member of the DnsUpdateProxy group |
Prove the cause before changing anything
These checks only read.
- In Event Viewer, open the System log and find event 1056. Note the time and that the source is
DhcpServer. - See what is configured now. From PowerShell on the DHCP server, or remotely with
-ComputerName:
Get-DhcpServerDnsCredential -ComputerName "dc02.contoso.com"
Microsoft says the cmdlet gets the domain name and user name for the account the DHCP Server service uses to register or deregister client records on a DNS server. Microsoft's page does not show sample output.
- Check the account exists and is enabled, if one is returned, in Active Directory Users and Computers. Microsoft says the account should not be set to expire or carry other restrictions.
- Check DnsUpdateProxy membership. Find the group in Active Directory Users and Computers and read its members. If the DHCP server's computer account is there, the DNS records it registers are not secure by default, which is Microsoft's stated disadvantage of the group.
- Check the DNS zone's dynamic update setting in the DNS console. Microsoft's page names the secure-only zone as one of three conditions that need a dedicated account.
Read the results this way. Event 1056 together with no user name in the Get-DhcpServerDnsCredential result points to missing credentials. A DHCP server in DnsUpdateProxy with no credentials means records are unsecured.
Fix
Microsoft says you must create a dedicated user account and configure the DHCP servers with its credentials when three things are true: the DHCP server performs DNS dynamic updates for clients, a domain controller functions as a DHCP server, and the zones accept only secure dynamic updates. Without the account, "secure updates will not work".
Create the account. Use a dedicated domain user. Microsoft's event 1056 page says any valid existing user account will do, such as a Domain User account, and that it should not be set to expire or have other restrictions. Multiple DHCP servers can use the credentials of one dedicated account, according to the DnsUpdateProxy page. As advice, give it no more rights than a Domain User has.
Risk: creating the account adds a permanent, non-expiring credential to your directory, and anyone who learns its password can act as that account. Microsoft's pages describe no undo; to back out, disable or delete the account only after you have replaced the credential on every DHCP server that uses it.
Set the credential. Choose one method.
Disruptive step: setting the DNS credential changes the account that the DHCP Server service uses for DNS updates from then on. To back out, replace the credential with the previous account; Microsoft's pages document no step to remove records already created.
PowerShell, which prompts for the password:
$Credential = Get-Credential
Set-DhcpServerDnsCredential -Credential $Credential -ComputerName "dc02.contoso.com"
Both lines are from Microsoft's cmdlet examples. If you leave out -Credential, the cmdlet prompts for a user name and password.
DHCP console: right-click the DHCP server (Windows Server 2003 page) or IPv4 (Windows Server 2008 page), choose Properties, open the Advanced tab, click Credentials, type the user name, domain and password, and click OK.
netsh (from the event 1056 page): at a command prompt run netsh, then dhcp server <ipaddress>, then set dnscredentials <username> <domain> <password>, then quit.
Risk: the netsh form puts the password on the command line, where it can appear on screen and in command history. The PowerShell and console methods prompt for it. The page does not address history, so prefer the prompt methods.
DnsUpdateProxy. Microsoft describes the group as a way to avoid stale records when one DHCP server fails and another cannot update names the first created, because only the owner of a name can update it. All DHCP servers in the group can update each other's records. The cost is that names registered by a member are not secure by default. For a zone that allows secure updates only, Microsoft says to create a dedicated account and configure its credentials on the DHCP server so records are secure.
Risk: adding a DHCP server to DnsUpdateProxy lowers the protection on records it registers. If you add one, set credentials as well. To back out, remove the server from the group. Microsoft's pages do not say what happens to records already registered, so check them in the zone afterwards.
Confirm the fix
Get-DhcpServerDnsCredentialshows the domain and user name you set.- No new event 1056 appears in the System log after the change.
- A client that gets or renews a lease has its DNS records registered in the zone, and the account you set is able to update them. Test with one machine before assuming the whole scope works.
Example (illustrative): dc02.contoso.com hosts DHCP and DNS for CONTOSO. Its scope 10.0.20.0/24 has 254 usable addresses (256 less the network and broadcast addresses) and 180 active leases, which is 70.9 per cent (180 ÷ 254). Event 1056 is logged. The administrator creates CONTOSO\svc-dhcpdns as a Domain User with a password that does not expire, runs Set-DhcpServerDnsCredential with it, and confirms with Get-DhcpServerDnsCredential. A test laptop renews its lease, and the administrator checks its record in the zone.
What to watch afterwards
- Rotate the account's password on a plan that updates the DHCP credential in the same change. Microsoft says the account should not expire; a manual rotation still has to be matched on every DHCP server that uses it.
- If you add a second DHCP server or a failover partner, give it the same credential. Microsoft says several servers can share one account.
- Watch for DNS records that DHCP created before the credential existed. They belong to the old owner and may not update under the new account; Microsoft's pages do not describe a bulk fix.
- Microsoft says that without credentials you should run the DHCP and DNS services on different computers, and that with both on the same domain controller it strongly recommends credentials.
Read next
Related articles you may want next.
- TroubleshootingDHCP server "not authorized" in Active Directory: why it stops leasing addressesEvent 1046, a red down arrow on IPv4 in the DHCP console, or error 20070 when authorising. Check whether the server is in Active Directory's authorised list, why it dropped off, and how to authorise it again so it keeps leasing.Read article
- TroubleshootingClean Up Stale AD DNS Records: Scavenging Without Deleting Live OnesStale DNS records in an AD-integrated zone? Understand no-refresh and refresh intervals and timestamps, list records by age first, then enable scavenging on one server safely.Read article
- 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
Risks and limits
These commands have not been run or lab-tested. The event 1056 page is written for Windows Server 2003 and the DnsUpdateProxy page is archived material for Windows Server 2008, so check menu names on your release. The PowerShell cmdlet pages cover Windows Server 2016 to 2025. Microsoft's pages do not say what the DHCP server does with client registrations while no credential is set beyond the statements quoted here, and they do not describe moving existing records to a new owner.
Sources
- Event ID 1056 after installing DHCP — Microsoft Learn, page dated 2026-02-12, accessed 18 November 2026
- DNS Record Ownership and the DnsUpdateProxy Group — Microsoft Learn (archived), page dated 2012-08-20, accessed 18 November 2026
- Set-DhcpServerDnsCredential — Microsoft Learn, date not shown, accessed 18 November 2026
- Get-DhcpServerDnsCredential — Microsoft Learn, date not shown, accessed 18 November 2026
This article was originally published on .