We currently have a Windows 2000 Active Directory. Our main server incurred a major hardware failure, and the system state was restored, but there are group policy problems. The replicating DC is not accessible either. This server is 5 years old and will be replaced next week. I am choosing not to migrate up to AD 2003, and will do a fresh install. I prefer not carrying over any AD problems to the new domain.
Right now we are single domain office. In the near future we will establish a trust with another company's 2003 domain. What I want to do is setup the new 2003 domain while the existing 2000 domain (mskpc.com) is operational. When I installed the 2000 domain I specified the full dns name as mskpc.com instead of mskpc.local or mskpc.internal. Everything has worked fine with the .com extension until we decided to outsource our web site. We could not access our site internally. I had to add a dns record to allow it. We also host an Exchange 2000 server, and works fine as is so I left everything alone since there were no complicatoins.
Anyway, now I want to setup the new domain parallel to the existing one without disrupting operations. I would like to use a full dns name of "law.local" so that it does not interfere with the existing domain, and then add the exchange 2000 server to the law.local domain. Will this work? Will the law.local domain internal domain work as far as routing internal/external dns queries, and that applies to mail too? Thanks for any feedback.