Domain FQDN name being resolved to the wrong Domain Controller's IP
Posted on 2011-09-23
Our domain has 8 DC's. One of them had some problems with sysvol replication so, by the time we were working on fixing this issue, we stopped netlogon and ntfrs services to guarantee no user logons on it and no replication traffic occurs.
The problem is, even when users logs on othere DC's, sometimes the UNC Path \\domain dns name\sysvol was resolved to the IP of this domain controllers that was out for maintenance.
Since this DC has no sysvol share on it yet, the GPO's failed to be applied and many errors was raised at user's computers.
I know this may be related to DNS round robin feature. Is this correct? Souldn't \\domain dns name be resolved to the DC where user logged on? How do I workaround of this problem?