Hello,
I recently created a new Active Directory domain for our development environment - domain A. Up until I did this, all of our servers and workstations were kept in the same top-level domain - domain B. I set up the new domain A to be a forest with a two way trust with the old domain B. For the most part, everything works OK in the new domain, but I have yet to set up any machines in domain A to run the Active Directory DNS service. Currently, all of the machines in domain A point to the standard primary DNS server in domain B. The DNS server in domain B handles both the active directory info (_msdcs, _tcp, etc...) as well as the web host records.
I would like to get all of the active directory DNS info for the new domain switched over to a machine in that same new domain. Meanwhile, the old DNS server in domain B will continue to host the web site info ( etc.). I want to keep them seperate for both security reasons and that the update from NETSOL will take too long.
I tried setting up the AD DNS config last night in domain A, but the old DNS server somehow picked up the machine in domain A running DNS and added it to the list of top-level hosts. So, people coming to my website were either hitting the correct machine listed in the old DNS or the machine in the new domain where I had just set up AD DNS. I shut down the DNS server in the services on the new DNS machine, but I'm afraid that the server in the old domain will get confused and keep sending web traffic to the wrong server. Thus far, AD has been very aggressive in assuming which machines do what.
Anybody have any experience with something like this?
I recently created a new Active Directory domain for our development environment - domain A. Up until I did this, all of our servers and workstations were kept in the same top-level domain - domain B. I set up the new domain A to be a forest with a two way trust with the old domain B. For the most part, everything works OK in the new domain, but I have yet to set up any machines in domain A to run the Active Directory DNS service. Currently, all of the machines in domain A point to the standard primary DNS server in domain B. The DNS server in domain B handles both the active directory info (_msdcs, _tcp, etc...) as well as the web host records.
I would like to get all of the active directory DNS info for the new domain switched over to a machine in that same new domain. Meanwhile, the old DNS server in domain B will continue to host the web site info ( etc.). I want to keep them seperate for both security reasons and that the update from NETSOL will take too long.
I tried setting up the AD DNS config last night in domain A, but the old DNS server somehow picked up the machine in domain A running DNS and added it to the list of top-level hosts. So, people coming to my website were either hitting the correct machine listed in the old DNS or the machine in the new domain where I had just set up AD DNS. I shut down the DNS server in the services on the new DNS machine, but I'm afraid that the server in the old domain will get confused and keep sending web traffic to the wrong server. Thus far, AD has been very aggressive in assuming which machines do what.
Anybody have any experience with something like this?