The reverse lookup zone exists, and I can add entries to it manually, but it doesn't automatically populate.Dynamic updates are enabled for both the forward and reverse zones. This could be due to a couple of different things: 1) Are your clients obtaining IPs via a Windows DHCP Server?
Then check the Security tab on the Reverse Zone and make sure that group is authorized to create all child objects (DNS records) 2) If your statically-configured hosts are not updating the reverse zone, make sure their NICs are configured to register their IP in DNS (Windows hosts are enabled for this by default).I tried restarting the DHCP server the Full server sevral times but no success.The settings hasn't been changed, but I checked and it has a lot's of free IP -s and the scope is activated and the server is Authorized to serve DHCP."I checked and it has a lot's of free IP -s" Not what the system is telling you. this is how your local hosts find the server and each other. the local dns server if it encounters a request it cant resolve like google it send the request to the dns servers listed in the forwarding.I would suggest a review or post screen shots of what you are seeing that tells you you have available ips. Did this server crash or recovered from virus/malware? lease time and dns on the workstation is correct and looks good.
The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.