We are eliminating a domain controller in our Maine office to reduce costs. Currently the DC in Maine is running DHCP and in an effort to keep DHCP local to the office, we have installed DHCP on a plain, old Windows 2003 server that will remain in the Maine office and we have deactivated the scope on the Maine DC.
Note that the domain controller in our Maine office is also runniing DNS and the DNS zone where dynamic DNS registrations occur is located on this DC and the forward and reverse zones are defned as active directory integrated zones as all of our DHCP clients in 12 states register in the same zone. As soon as we remove the domain controller from the Maine office the site definitions for this office will become part of the site defined in our Connecticut office. Note that the Connecticut DC is also running DNS and it too contains the same AD integrated zones found on the current Maine DC. Once the Maine DC goes away, the dynamic DNS registrations will need to be made through the Connecticut DC or another DC somewhere in another office.
To complicate things a bit more, we also decided that we would also install DNS on the same plain, old Windows 2003 server that will remain in the Maine office. The idea was to keep DNS queries local to the office by creating secondary copies of all zones located on the Connecticut office domain controller.
After we installed DNS on the plain, old Windows 2003 server with secondary zones we installed DHCP on that same server and we activated the scope while at the same time deactivating the same scope on the DC. When a client registers itself with DHCP on the plain, old Windows 2003 server we have DHCP setup to automatically perform DNS dynamic registrations on behalf of the cleint and since the DC in the Maine office is still active, we expected there wouldn't be any problems with the clients registering in DNS on the domain controller until we removed the DC and moved the site.
Our problem is this.......
If we clear out the forward and reverse lookup zones for a workstation in the Maine office and renew the workstation's lease via an IPCONFIG command, we note that the DNS registrations are being made and zones on the domain controller are being dynamically updated. IN DHCP, however, the little client icon next to the address indicates that the DNS registration was not successful and the logs for DHCP also show that the registration was not successful. Since we can obviously see that the dynamic DNS registrations ARE being made we are trying to determine why DHCP shows that the registrations are not being made. Does anyone know how we can make DHCP understand that the DNS registrations are being made successfully?
My guess is that it has something to do with DNS and DHCP being on the same Windows 2003 server and the zone in DNS are only secondary copies. What we are looking for is some way for DHCP to understand that it needs to confirm the dynamic DNS regisrations are taking place on a different DNS server.
Any help in resolving this would be greatly appreciated.