Some of you may find this question very interesting.
Background: I am running into a situation where my Active Directory is not functioning at all and I had it working very good before that. Recently I have added web service to this machine and migrated IIS from Win 2K server. BTW my AD is wrunning on Windows 2003 server.
Problem: After I have the machine runing IIS, I found out one fine day that my dns is totally messed up. The domain I used to use is no more valid one. When I run "nslookup lab.com" it gives me some weried IP address. The site "lab.com" exists in the web and as if my AD is trying to connect to that domain and earlier it was only my domain inside our subnet. Since, AD crashed, DHCP also crashed.
Now I have been advised by my senior Computer guys, to use another existing domain for AD. This domain is named "lab.university.ca"( no chance of being duplicate). The machine that is running this domain and dns service won't be part of the domain, so I don't understand how will my AD work as Domain controller for this domain? As far my understanding about AD I know that I have to have an operational domain and at the same time I need to have it on the same server. Am I right or wrong?
Secondly how my DNS got messed up? How can my server starts trying to talk to a domain which is not at all in our physical network. I can have similar domain like other commercial website has, but it should not be a problem as long as I have it inside my subnet. But what could cause this kind of situation?
Finally, what should I do to configure my AD? Can I stick to my old domain " lab.com" and how or should I need to change the domain?
FYI, for few days I had all service running very smooth on the server until I come across this problem. I would appreciate all your expert comment and advice.