Dns clients not updating records
If you elect to use the entries in a search list, the resolver ignores the primary suffix, its parents, and the connection-specific suffix.
Murphy and other elements of chaotic cosmic calamity.
If the TCP/IP settings for a member computer specify the IP address of a public DNS server—perhaps at an ISP or DNS vendor or the company’s public-facing name server—the TCP/IP resolver won’t find Service Locator (SRV) records that advertise domain controller services, LDAP, Kerberos and Global Catalog.
Without these records, a member computer can’t authenticate and get the information it needs to operate in the domain.
This automatic updating, called Dynamic DNS Updates service, reduces the administrative overhead associated with manually administering DNS records of network hosts.
While this service can reduce administrative overhead, it also can, and does, have deleterious effects on the larger Internet by leaking traffic regarding private IP addresses that should never leave the local area network.
You do not need to disable dynamic DNS updates if: However, if you have configured your host to act as a DHCP client/server and you make use of the private IP address space (including 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16) specified in RFC1918, you should turn off the dynamic DNS update feature.