I've got a DHCP server that's configured to "Always dynamically update DNS records". Unfortunately, it's not doing its job. The client sends an Option 81 with its FQDN and all flags at 0. The ACK back from the server does not contain Option 81, and a PTR record never appears. A records are appearing properly, for what it's worth.


I believe I have resolved the problem, today, by configuring the DHCP server to use explicit credentials when performing DDNS updates. Perhaps I'm remembering incorrectly, but I don't believe this was a requirement in Server 2003.

I started by creating a non-privileged user account set with a strong password, password does not expire and user cannot change password.

To configure DHCP:

  1. Open the DHCP console using my administrative account.
  2. Add all authorized DHCP servers to the console.
  3. For each DHCP server, remove the explicit update credentials:
    1. Expand the server node.
    2. Right-Click the IPv4 Node.
    3. Click the Properties menu item.
  4. Click the Advanced tab.
  5. Click the Credentials button.
  6. Enter the credentials for the newly created user.

After configuring the explicit credentials, I issued an ipconfig /renew to my own workstation. The PTR record appeared immediately in DNS. This has a secondary benefit in that a failover DHCP server will have access to update records that were initially created by the primary DHCP server for the scope.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.