*** Updated by Wrobinson on 4/18/08 *** Do not connect the copy of the Active Directory environment on the production network under any circumstances, even if the IP address and computer name is changed. Severe consequences can result, including the corruption of AD beyond repair, requiring it to be recovered from backup. You need to isolate these two environments completely, which will eliminate the need to re-IP and rename servers. In some instances, a firewall is used to provide such isolation but the best method of doing so is for the two separate networks not to have any common thread what-so-ever. *** End update *** Changing your IP address on an Active Directory Domain Controller can cause many issues with the DNS server on that machine. To change the IP address complete the following steps: Select: Start Settings Network and Dial Up Connections Select: Your Local Area Connection Select: Internet Connections (TCP/IP) Properties Change: Your IP Address and Subnet Mask and Gateway Change: Preferred DNS server's address to the new server address Select: OK OK Close Your server's address is now changed Select: Start Programs Administrative Tools DNS Double click Forward Look Up Zones Double click your server name Delete: Your type A records Reset your information in your SOA and NS records Exit DNS Drop down to a MS DOS prompt and type the following: ipconfig /flushdns Enter Net Stop DNS Enter Net Start DNS Enter Net Stop Netlogon Enter Net Start Netlogon Enter ipconfig /registerdns Enter You can now go back to DNS and make sure the records were all created and they should have changed the address to the correct address on their own. Now run nslookup from a MS DOS prompt and see if all is resolved OK or not. It the names and IP addresses all resolve correctly you are correct. If not then go back to nslookup and do the following: I found I had to type set root=000app02.now.com (the name of my DNS Domain) and hit enter When the prompt returns type exit to exit out of nslookup. Then when I typed nslookup it resolved the name correctly.

*** Updated by Wrobinson on 4/18/08 *** Do not connect the copy of the Active Directory environment on the production network under any circumstances, even if the IP address and computer name is changed. Severe consequences can result, including the corruption of AD beyond repair, requiring it to be recovered from backup. You need to isolate these two environments completely, which will eliminate the need to re-IP and rename servers. In some instances, a firewall is used to provide such isolation but the best method of doing so is for the two separate networks not to have any common thread what-so-ever. *** End update *** Changing your IP address on an Active Directory Domain Controller can cause many issues with the DNS server on that machine. To change the IP address complete the following steps: Select: Start Settings Network and Dial Up Connections Select: Your Local Area Connection Select: Internet Connections (TCP/IP) Properties Change: Your IP Address and Subnet Mask and Gateway Change: Preferred DNS server's address to the new server address Select: OK OK Close Your server's address is now changed Select: Start Programs Administrative Tools DNS Double click Forward Look Up Zones Double click your server name Delete: Your type A records Reset your information in your SOA and NS records Exit DNS Drop down to a MS DOS prompt and type the following: ipconfig /flushdns Enter Net Stop DNS Enter Net Start DNS Enter Net Stop Netlogon Enter Net Start Netlogon Enter ipconfig /registerdns Enter You can now go back to DNS and make sure the records were all created and they should have changed the address to the correct address on their own. Now run nslookup from a MS DOS prompt and see if all is resolved OK or not. It the names and IP addresses all resolve correctly you are correct. If not then go back to nslookup and do the following: I found I had to type set root=000app02.now.com (the name of my DNS Domain) and hit enter When the prompt returns type exit to exit out of nslookup. Then when I typed nslookup it resolved the name correctly.