Link to home
Start Free TrialLog in
Avatar of scusack
scusack

asked on

When I do "nslookup or ping mydomain.local" in my local site the domain controller of the remote site responds not the dc of my local/current site.

When I do "nslookup or ping mydomain.local" in my local site the domain controller of the remote site responds not the dc of my local/current site. But I know that the local dc is working. The local DCs should respond first before the other DCs at the remote site. How can I fix this issue in Windows Server 2003 environment?

Thanks
Avatar of dhruvarajp
dhruvarajp
Flag of India image

This is not the issue,
the remote domain controller is the primary dns server for the dns zone yourdomian.locla
that is why that domain conroller is responding to nslookup and  ping

that is it. and that should be fine unless you want dns resolution to happen in this site
as dc are choosen by  clients and most applications (exchage) in the locat site only (whenever available)





Avatar of als315
In nslookup you get answer from first DNS from list in TCP/IP properties.
Check this list. Have you answer from first DNS in list?
May be it is server with multi network adapters?
Avatar of scusack
scusack

ASKER

We basically, don't want one site to query from remote site's DCs as long as the local site's DCs are working. Most of our sites are connected through a microwave link(E1) and we want to utilize that link for other purposes such as internet, voice, VTCs, and email. Workstations/servers should only query on its local DCs unless it is down. Is there any workaround to do that?

Thanks.
ASKER CERTIFIED SOLUTION
Avatar of dhruvarajp
dhruvarajp
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of scusack

ASKER

Works