To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Answer is to replace ddns-rev-domainname from "1.168.192." to "".
1000 clients (Win XP & Win7), and from what I can tell it affects highly mobile users more than anyone else.
For those companies considering an upgrade to Microsoft Windows Server 2008, it is very important to understand how DHCP and DNS work together to power Windows Server 2008.
In this post, you will learn how to configure DHCP to dynamically collaborate with DNS and WINS in Windows Server 2008.
Otherwise, DHCP assigns the hostname, and again DHCP updates DNS.
Hello everyone, I have a strange problem and I can't seem to see anything that could cause it.
The way we solve this is by manually deleting the offending records and issue "ipconfig /registerdns" on the client.
No error is logged in the event viewer of either the client and the server.
I've followed a few how-tos online and managed to get it working, with one exception that my reverse zone doesn't seem to be getting updated correctly. $TTL 907200 ; 1 week 3 days 12 hours 1.168.192.IN SOA As we noticed that only Windows 7 workstations with a static IP were being registered we started troubleshooting.As an AD guy I was 100% confident we could get this done using GPO’s.The DHCP server is setup to always update both A and PTR record.The problem is that the PTR aren't actually updated and, sometimes, the A record isn't either.