Hi Everyone, I have 3 DNS servers (win2k3) integrated into AD that their reverse DNS is not updating. Both Forward and reverse DNS was screwed up to begin with.To fix the forward, i modified the DHCP server to always update DNS when ever it adds a new client.As we noticed that only Windows 7 workstations with a static IP were being registered we started troubleshooting.
To learn more about DNS, feel free to visite Wiki page 5. To prevent us from to much network traffic because of DNS replication, we do not replicate the zone over the complette forest, we replicate only in this domain. After this you have to select the IP Version that will be handled by this zone. “Allow both nonsecure and secure dynamic updates” could be a entrace for Haks (DNS spoofing). Now you get a short summary and you can create the zone by clicking “Finish”. If all works fine you should see the new zone in you DNS MMC.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. The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.The problem is this: when the network adapter is configured for DHCP and the DHCP server doesn't register DNS records on behalf of its clients (because it can't, or because it's not configured to do so), then A friend not on SF said: "That's normal, PTR is only updated by DHCP in Win2K ".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?Update [27/06/2013]: new information regarding the topic: Windows 7 & Reverse Lookup DNS Registration [Update] In my current project we have an Active Directory domain where we use Windows DNS servers with domain integrated DNS zones.For the reverse lookup zones we configured secure only updates.This would mean when the default flag of "0" comes in the server will then try to register the PTR record with the DNS server(s) it is configured to update.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.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.