Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix Event ID 1056

Event ID 1056: DHCP has no credentials for dynamic DNS registration on a DC

9 min read Updated October 5, 2026 Windows Server: AD, DNS & Group Policy

Fix it now

The DHCP service has noticed it is running on a domain controller with no credentials configured for the dynamic DNS registrations it makes on behalf of clients. Without them it registers those records as the domain controller itself, which has full control of every DNS object. Give it a plain domain user account instead.

Run these on the DHCP server in an elevated PowerShell session

Set-DhcpServerDnsCredential -Credential (Get-Credential) -ComputerName dhcp01.contoso.com
Get-DhcpServerDnsCredential -ComputerName dhcp01.contoso.com
Restart-Service DHCPServer
  1. Create an ordinary domain user account for the job first. It needs no group membership beyond Domain Users, and its password must not be set to expire.
  2. The same setting is in the DHCP console: open the properties of the server, go to the Advanced tab and select Credentials.
  3. From a command prompt the documented equivalent is netsh dhcp server <ipaddress>, then set dnscredentials <user> <domain> <password>.
  4. Watch the audit log in %windir%\System32\Dhcp afterwards: ID 30 is an update request, ID 32 is one that succeeded, ID 31 is one that failed.

Use the same account on every DHCP server that serves the same clients, including failover partners, so the records they create all have the same owner.

The warning stops once the credential is set and the service restarts. The next section explains why Microsoft treats this as a security configuration rather than a cosmetic warning.

Why it happens

Event ID 1056 is a warning, logged by DhcpServer in the System log, and its text says exactly what it is: the DHCP service has detected that it is running on a domain controller and has no credentials configured for use with dynamic DNS registrations initiated by the service. Nothing has failed. Leases are being issued and records are being written.

The problem is which identity writes them. With no credential set, the DHCP Server service runs under the domain controller’s computer account, and Microsoft’s own description of the consequence is blunt: that account has full control of all DNS objects, so records registered dynamically are open to being overwritten. On a zone set to secure updates only, that is precisely the protection you thought you had, quietly not applying.

The fix is one account and one dialog, and it is worth doing on member servers too. Microsoft’s guidance is stronger than the event suggests: use DNSCredentials when DHCP and DNS run on the same domain controller, and if you are not going to, run the two services on different computers.

No credential has ever been configured

You have this one if The warning is in the System log and the Credentials dialog in the DHCP console is empty.

  1. Create a dedicated domain user account with a strong password and no administrative rights anywhere.
  2. Set it with Set-DhcpServerDnsCredential, or in the server’s properties on the Advanced tab, Credentials.
  3. Restart the DHCP Server service and confirm the warning is not written again.

Treat the password like any other service credential. If it expires and nobody notices, registration fails quietly and the audit log fills with ID 31 lines.

The credential is set but updates still fail

You have this one if ID 31 lines keep arriving in the audit log after the change, naming records that could not be written.

  1. Sign in with the account once to prove the password is right and the account is not locked or expired.
  2. Confirm the zone accepts dynamic updates and is set to secure only rather than none.
  3. Check whether the records in question are already owned by another identity, which stops the new account updating them.

Records created before the change still have the old owner

You have this one if New devices register cleanly while long-standing ones never update, and their addresses stay wrong after a device moves.

  1. In DNS Manager turn on View, Advanced, then open a stale record’s properties and read the Security tab to see who owns it.
  2. Delete the affected records and let DHCP or the client recreate them under the new identity.
  3. Enable the scope option that discards forward records when a lease is deleted, so the cleanup keeps happening on its own.

Deleting records means a short window where those names do not resolve. Do it outside working hours for anything that matters.

Two DHCP servers are registering under different identities

You have this one if A failover pair or two scoped servers keep failing to update each other’s records for the same clients.

  1. Set the same credential account on every DHCP server that serves those clients.
  2. Restart both services and let a full lease cycle pass.
  3. Confirm both servers now log ID 32 entries for the same client names.

Full reference

The three audit log entries to watch

Audit ID What it records
30 A DNS dynamic update request was sent to the DNS server
31 The DNS dynamic update failed
32 The DNS dynamic update succeeded

A healthy server writes 30 followed by 32. A run of 31 lines after you set the credential is a different problem from having no credential at all: the account exists and is being used, and something about it or the zone is refusing the write. The files sit in %windir%\System32\Dhcp, one per day, comma-delimited.

Setting the credential three ways

Route Command or path
PowerShell Set-DhcpServerDnsCredential -Credential (Get-Credential) -ComputerName <server>
Read it back Get-DhcpServerDnsCredential -ComputerName <server>
Netsh netsh dhcp server <ipaddress> then set dnscredentials <user> <domain> <password>
Console Server properties, Advanced tab, Credentials

The account can be any valid existing user account, such as a Domain User. It should not be set to expire and should carry no other restrictions – Microsoft says this explicitly, because an expiring password turns a security improvement into an outage three months later.

Why this matters more on a domain controller

On a member server the registration identity is that server’s computer account, which is unremarkable. On a domain controller it is the domain controller’s own account, and that account can rewrite any DNS object. Every host and pointer record DHCP creates on behalf of a client is then owned by an identity with authority over the whole zone, which is why the service raises a warning about a configuration that is otherwise working perfectly.

Related events and where they are not

  • 1056 is in the System log with source DhcpServer, and it is a warning, not an error. If you are filtering for errors you will never see it.
  • The 30/31/32 entries are in the audit text files, not in Event Viewer. Looking for them as Windows event IDs finds unrelated events.
  • If DHCP itself is not serving clients at all, this is the wrong article: look for 1046 (not authorised) or 1059 (could not see a directory server) instead.
  • If records exist but resolve to the wrong host after devices move, check the scope’s DNS settings for dynamic update behaviour and record discarding before blaming the credential.

One account, every server

The value of the credential comes from consistency. If server A registers as one identity and server B as another, each one owns the records it created and neither can maintain the other’s. That is the failure mode that turns up months later as a name pointing at the wrong machine after a device changes address. One dedicated account, used on every DHCP server that serves the same clients, removes the class of problem rather than the symptom.

Every code this article covers

Code What it points at Source
Event ID 1056 DHCP is running on a domain controller with no credentials configured for the dynamic DNS registrations it makes for clients Microsoft Learn
Event ID 31 DHCP audit log entry: a DNS dynamic update failed Microsoft Learn
Event ID 30 DHCP audit log entry: a DNS dynamic update request was sent to the DNS server Microsoft Learn
Event ID 32 DHCP audit log entry: a DNS dynamic update succeeded Microsoft Learn

Confirm the fix worked

  1. Event ID 1056 is not written again after the service restart.
  2. Get-DhcpServerDnsCredential returns the account you configured.
  3. Force a client to renew and confirm the audit log shows ID 30 followed by ID 32.
  4. Open that client’s record in DNS Manager, Advanced view, and confirm the credential account is the owner on the Security tab.
  5. On a failover partner, confirm it can update the same record without writing an ID 31 line.

Questions people ask about this

Is there anything to buy to clear this warning?

No. It is one domain user account and one dialog. Nothing about the fix involves a product or a licence.

Does the account need administrative rights?

No, and it should not have them. Microsoft says any valid existing user account, such as a Domain User, will do. It only has to be able to create and update records in the zone.

Should DHCP run on a domain controller at all?

It works and plenty of organisations do it. Microsoft’s position is that if you do, configure DNSCredentials; if you are not going to, run DHCP and DNS on different computers.

What happens if I ignore the warning?

Nothing visible at first. The cost arrives later as client records owned by the domain controller account, which is the identity you were trying to protect the zone from in the first place.

Do failover partners need the same account?

Yes. Records are owned by whoever created them, so a partner using a different identity cannot maintain the records the first server wrote.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Event ID 1006: Group Policy cannot authenticate to Active Directory Free Fix Error 8453 replication access denied: repairing AD replication permissions License Error FRS Event ID 13508: SYSVOL still on File Replication Service and unsupported License Error Error 8340: metadata cleanup after a domain controller that never came back
โ† Back to Knowledge Base