Domain FQDN name being resolved to the wrong Domain Controller's IP

Hi Experts,

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?


Rodrigo Garcone

Who is Participating?
snusgubbenConnect With a Mentor Commented:
It is not given that the client will use the authenticating DC. It will most likely send DNS requests to the DC that is set on the clients NIC. But the authenticating DC may answer the client to use another DC to access resources.

You can authenticate towards DC1 but the client can be routed to DC3 for SYSVOL. DCs are multi-masters, so you can't be sure which DC the client use for accessing resources.
SandeshdubeySenior Server EngineerCommented:
You can change the dns setting on the client PC to point to other DC.
Also in Active directory sites and service map the subnet to other site.
But if the sysvol issue on the server can be fixed early you can ignore this error on the client end.
nslookup <domain FQDN> should return all your DCs, so what you see is normal.

If the problem DC is not holding SYSVOL, you should try to reinitialize it with setting the Burflags registry key to "D2" (hex).

garconerAuthor Commented:
Dns on clients is already pointing to others dcs. If i type in \\domain name at the workstation with the problem, it resolves to the server with error, even when user is authenticated on other dc. Why the domain dns name is not being resolved to the user' logon dc?
garconerAuthor Commented:
Tks! That's what I expected.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.