We currently have a flat network between seven schools in our school division using LANSPAN. Their is only one router in the network at our Central Office where all Internet traffic comes through. There is only one DHCP server at the Central office which serves all the schools. This dhcp server (Windows Server 2003) is installed on the main domain controller (along with DNS) and each school has a server which is part of the same domain (secondary servers). The DHCP server is configured to have one scope - 172.16.16.0 through to 172.16.20.255 to hand out IP addresses for all clients throughout the division's schools. The problem is that while DHCP is functioning properly, the resource records (A records) are not being recorded in DNS. I thought this was suppossed to happen automatically. The zone is AD integrated, the IP addresses are being assigned via DHCP, DHCP option "Discard A and PTR records when lease is deleted" is turned on. I have forced DHCP to own the record rather than choosing the option to dynamically update DNS A and PTR records only if requested by the DHCP clients. I have added the DHCP server to the DNSUpdateProxy Group I have set Option 015 to the the AD domain name I have set Option 006 to only the internal DNS servers I have created and configured a user account for use as credentials for DHCP to register clients that are not part of the domain. Scavenging has been set at both the server level and the zone level. Any thoughts as to why the DNS resource records are not registering in DNS.
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!