Hi guys
I want to discuss this with you. Now I have one Domain and all computers in our organization are joined to this domain. Actually we have 2 Buildings. The length between them is 150 K.M. Okay now let’s say the DC is located in Building 01 and we have Primary DNS in Building 01 and Secondary DNS in building 02. The user when he/she wants to login, the Authentications will getting from the DC in Building 01. That means, the load will be on one Server. Okay, Is there any way to let only the DNS in Building 02 to Communicate with DC and the Clients get the communication with the DNS which is registered on it (DNS Suffix)

Why use primary and secondry DNS Servers ?, just use AD integrated DNS for multiple DNS Servers.

Okay. I said Location 01 has the DC and Primary DNS Server. And Location 02 has Secondary DNS Server. But the user when he login, the Authentication will get it from location 01. means from DC
I want all PCs in Location 01 to get the authentication from Primary DNS
and all PCs in location 02 to get the authentication from Secondary DNS

Then change the setup so DNS is AD integrated then theres no Primary / secondry.

I think you need to understand your terminology better, DC Authenticate you on to a domain, All DNS do is resolve names for your internal (and perhaps external) networks, so turns \\servername into 10.xx.xx.xx. What I recommend you do is turn the DNS server 2 into an Secondary domain controller, enable that to be a global catalogue server, and that will share the load across the 2 servers for logon, I am not sure if you can make site1 logon to dc1 and site2 logon to dc2 ect, but I am looking. Jason might be able to help here

Yes AthlonGod, on each DNS Server there is an AD . But the first or the primary AD is located in Location 01.
I have another solution, which is creating child domain on location 02 but I don't want to do that for some reasons.
I think there is a way to create sites and let specific subnet to get the authentication from for example site A and the other from site B ... etc.
if all clients getting the authentication from the Primary DC, the Link between the locations will be utilized (To much traffic) and I want to free it.

You could try in your environment variables to use the command logonserver=servername on the local Workstation and see if that works, I am unsure that it will but it is worth a try.

To see if it has worked type set at the command prompt.

Try using sites and services part of AD and change the cost of the links maybe.