I've run into a strange one. Today I noticed that clients weren't registering their A records in DNS.
- AD integrated zone - dynamic secure updates enabled on the domain zone.
- Windows XP/ 7 clients
- DNS specific search suffixes are pushed out to PCs
- Primary DNS suffix is listed first
- All clients are members of domain
- Clients are receiving DNS Servers via DHCP
- Clients are receiving DNS domain name via DHCP
Scavenging settings have all been ruled out as the cause of the problem.
Proper functionality would be the clients use their primary DNS suffix to register their A record with the DNS server. However, this is not happening. The only way I have been able to get the clients to register correctly is to enable the "Register DNS records with connection-specific DNS Suffix" setting in TCP/IP settings.
I can push that setting out via GPO to get the clients to register, but this seems like a band-aide.
We have other sites/ subnets that have no issues dynamically updating their dns records. These sites/ subnets have DCs that replicate to the DNS servers that are not receiving the dynamic updates from our site.
The only difference I can find is that the sites that operate correctly do not have the DNS domain name set via Group Policy.
I plan to test tomorrow by creating a new subnet that does not push out the DNS Domain Name setting. I will then see if a PC on that subnet can register it's name without having to enable the connection-specific setting.
Until then, has anyone run into anything like this or have any suggestions?