How to setup an unregistered internal AD domain whilst creating a domain controller
Posted on 2004-08-10
I am simply trying to experiment with creating and modifying domain controllers, and learning how to use Active directory.
I understand that DNS is integral to this in resolving names to addresses and so on. The two DNS addresses that were automatically selected on my home ADSL router are 188.8.131.52 and 184.108.40.206 which I have traced back to my service provider. If I am setting up my own DNS under 2000, should I be disabling the DNS on my router first?
Second issue: How do I chose and employ a ficticious domain name without getting into trouble on the WEB. How can I be sure that my new unregistered experimental domain called BIGFIRM.BIZ will not create problems with other DNS servers on the web. I am assuming that any DNS server on my LAN will eventually connect up with others on the WEB to confirm or inform of the existence of my new unregistered domain BIGFIRM.BIZ, and create problems. I read something somewhere about being able to chose between an internal domain name and one which is connected to the WEB. I have an ADSL connection both here and at school. Does that mean that I can not have an internal domain? As you can see I am very confused.
Third issue: I tried to convert my win2000 advanced server to a domain controller for the first time. Half way through the process I was warned that "No DNS server could be found" , which surprised me because "ipconfig /all" showed clearly the above 2 DNS server addresses. "Do you want win2000 to setup a DNS server?" was the next question. Mark Minasi wrote in his book MASTERING WIN2003 SERVER do not say yes to this option here. It only leads to problems. Instead stop the installation and make sure the DNS server has been properly setup. Then install the domain controller.
I did not follow his advice. I followed Microsofts RECOMMENDED option and allowed 2000 to create the DNS server. Then when I tried to join the new domain on another 2000 pro PC, I got the message that the domain could not be found and that perhaps I had a problem with DNS.
I would really value some answers to the above 3 points, as I need to setup 2003 server as a domain controller and 20 domain clients in the next week at school.