Dns not updating from dhcp
For example, some folks believe that the DNS servers or other DCs not be running DHCP should be in it. Make sure that NO user accounts are in that group, either.(I hope that’s crystal clear – you would be surprised on the number of responses I get asking if the DHCP credentials should be in this group.) You Just to be crystal clear, this means that if the lease is an 8 day lease, than NOREFRESH should be 4 (four) and REFRESH should be 4 (four) so when you add them together, they are not greater than the lease length.This applies to Windows 2000 Professional and all newer operating systems.For domain controllers, due to the importance of keeping up to date and accurate SRV and other records, the Netlogon service will attempt to update these records every 60 minutes.If there is no timestamp, such as a manually created, static record, it will not get scavenged.Also, if all servers, including DCs, are automatically updating their own record, then there is no fear of losing their records, because for one, their records (timestamps) are current, therefore scavenging won’t touch them, and two, Windows Servers by default will update their records every 24 hours, with the exception of domain controllers at every 60 minutes..================================================================= There are some misconceptions prompting fears that Scavenging will remove everything in your zone, includind servers.Please understand, the main thing that scavenging works on is the timestamp.
In this mode, the DHCP server always performs updates of the client’s FQDN, leased IP address information, and both its host (A) and pointer (PTR) resource records, regardless of whether the client has requested to perform its own updates.” “With secure dynamic update, only the computers and users you specify in an ACL can create or modify dns Node objects within the zone.
Also by default, the creator owns the new object and is given full control of it.