If there are missing entries, you likely have your DHCP missing one of two settings: This is required if you have DHCP installed on a Domain Controller.
It is an issue on Server 2000, 2003, 2008, 2008R2, Server 2012, Server 2012 R2 and will likely be an issue in the newer builds.
I did a bit of reading and discovered that the group should have DNS computer accounts in, if the zones are configured to only be updated securely - which they were. I am forever getting incorrect / outdated lookups when connecting to machines.
I also read that a service account should be configured to carry out the zone updates - which I have now done. Our domain's zone is configured as an AD-Integrated zone with replication to all DNS servers in the forest.
Anyway, the w2k server is a domain controller and has dns, dhcp, roles, and so does the new w2k3 server, whick replaced a w2k server with the same roles.
Problem: Clients that get there ip address from the w2k3 server, do not dynamically update dns, but clients that get there ip addresses from the w2k server do, as they always have in the past.
When I joined the company, I noted that a lot of name lookups were failing or pointing at the wrong machines.
The only thing I changed to try and get it to work, was to change the dhcp - dns setting from dynamically update dns to always update dns.DNS stands for Domain Name System or Domain Name Server.It's only real purpose is to make browsing the Internet easier for people. Computers like to pull up websites using IP address numbers.At the same time, I'm combing through AD and rationalizing group memberships.The Dns Update Proxy group, despite its description, had a domain admin account and the BES Service Account as members.Before we do, just for good measure, verify that you can not pull up by name. You manually did the dirty work that the DNS server would normally do and it made no difference.