The local server that you are building must have DNS installed for it to work as a domain controller (yes, you must have a ".somthing" .local, .com, .org, .msft, .net, etc)
You seem to be building a new domain controller for a NEW domain. And it doesn't seem like you want this domain controller to be serving the existing domain....that you are creating a new domain.
With that said, you need to point the local TCP/IP properties of the new domain controller to point DNS to itself (not to the current DNS server).
In order for your clients to join the NEW domain, you must make sure that they have an IP address that is using your NEW DNS server only. In other words, the clients must not use the existing DNS server. The clients that you want to participate in your new domain must use the DNS server of your NEW domain.
However, the clients will not be able to join more then one domain at a time. Meaning if they join your new domain, they will no longer be a part of the old domain.
If you want clients to be able to use resources on BOTH domains (existing and new), you should create a TRUST relationship between the domains...
-hope this helps..
Joseph L. Poandl
MCSE 2003
If your company is in need of experts to examine technical problems/solutions, please check out
(Sales@njcomputernetworks.com)