in the TCP/IP settings of the network interface: As much as it may appear strange, this is the only solution to ensure Windows will register both the A and the PTR records for a DHCP network connection; otherwise, it will only register the A record. sends option 81 and its fully qualified domain name to the DHCP server and requests the DHCP server to register a pointer resource record (PTR RR) on its behalf.
The dynamic update client registers an address resource record (A RR). the DHCP server can be configured to instruct the client to allow the server to register both records with the DNS.
I can do a reverse lookup on the IP and that works but not name to IP. You might be able to do this by tweaking some group policy settings, or by running a script to bulk "ipconfig /registerdns" on a bunch of clients.If you insist on doing this from the server end of things, it should be possible to write a custom program to read the entries from a DHCP lease export, and register the addresses, but be sure to run it as the same account that DHCP uses for registrations, or else it may have trouble updating the entries in the future.And make sure the DNS dynamic update credentials are correct and appropriate permissions are applied for this to work As I said in the question, configuring the DHCP server is not an option. It won't register DNS records for its clients, period.They should be able to handle it, since all of them are domain members.That doesn't exactly seem to be the case from your experience, but might be close.... Massimo, are you able to pull a wireshark trace and check the DHCPREQUEST Packet?