I just started a new job and I have the unfortunate pleasure of fixing some rather serious issues with the network, so please bear with me.
I have a problem with our Windows Server 2008 Standard SP1 domain controller. We'll call it "DC01" for simplicity. DC01 is configured with DHCP and DNS. There is a reverse zone lookup that was created for the local subnet. The forward zone is working like it should. However, the reverse zone is NOT updating.
The client computers are just about all Windows 7 and them seam not to want to auto update. There is a couple XP machines on the network as well. The Windows XP computers are about the only computer that showed up in the reverse zone lookup. Just today I
The weird thing is when I right click the DHCP server and go properties --> DNS (tab) --> it's set to dynamically update A and PTR records (see image attached). So it *should* be updating reverse DNS, regardless of the Client PC's wishes, right?
Another issue that may or may not have anything to do with this, is there is a Windows 2008 Standard R2 server, we'll call it "Server01" that from what it appears used to be a Domain Controller running DNS. This server was not demoted properly. Active Directory still sorta thinks "Server01" is a domain controller. For a while it was listed on the Name Server's tab, I removed that about a week ago. DNS was not installed nor running on Server01 when I got here. Server01 still shows up in some of the _MSDCS.Domain.Local records. So, if DNS is active directory integrated, could this be the reason why? I plan to clean up "Server01" soon.
Any insight would be appreciated.