Rename Domain????
Hi
I'll be migrated one of my client Domain Controllers from Windows 2000 server to Windows Server 2008 R2. Their current internal domain is using .COM, their registered domain name is .COM also therefore, the internal domain and the external domain are identical.
The issue for now right now is when you try to resolve the internal domain name using NSLOOKUP, it returns their public ip address which is linked to their registered domain name.
Is it possible to rename their internal domain name to .LOCAL right after I migrated their Domain Controllers to Window Server 2008 R2 ? Is that possible ????? Any ramification of renaming the internal .COM domain to .LOCAL????
Appreciate your feedback
I'll be migrated one of my client Domain Controllers from Windows 2000 server to Windows Server 2008 R2. Their current internal domain is using .COM, their registered domain name is .COM also therefore, the internal domain and the external domain are identical.
The issue for now right now is when you try to resolve the internal domain name using NSLOOKUP, it returns their public ip address which is linked to their registered domain name.
Is it possible to rename their internal domain name to .LOCAL right after I migrated their Domain Controllers to Window Server 2008 R2 ? Is that possible ????? Any ramification of renaming the internal .COM domain to .LOCAL????
Appreciate your feedback
Hamid Reza Molahadi
I think you should setup a new domain with .Local and then migrate your .Com domain to it. it's more secure than renaming the current domain.
ASKER
Is that possible? How?
1) On the new server set the TCP/IP configuration
2) using the third party application like "Ideal Administration" to export the data of you domain controller such as "users account", "passwords", "groups", "memberships", "printers" and etc On the old server.
3) Offline the old domain controller.
4) promote the new server to domain controller with DNS integrated with the same name of old domain name.
5) Install same third party application on the new domain controller to import data you recently exported!
6) BOOM! you've a fresh domain controller with all data.
2) using the third party application like "Ideal Administration" to export the data of you domain controller such as "users account", "passwords", "groups", "memberships", "printers" and etc On the old server.
3) Offline the old domain controller.
4) promote the new server to domain controller with DNS integrated with the same name of old domain name.
5) Install same third party application on the new domain controller to import data you recently exported!
6) BOOM! you've a fresh domain controller with all data.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
if you have exchange 2007/2010 installed in the same domain, then you cannot change domain name
It will break exchange
It will break exchange
ASKER
@ rybaa, I'm a bit cautious particular migrating their primary DC and DNS server. I'm out of time testing your suggestion in the lab since migration starts tomorrow.
@ KCTS, I thought I've seen A record of www in the DNS server, I'll check this again I might be mistaken. If not I'll try your suggestion and if doesn't work i'll try the below link also which I just come across just now.
http://oddjobsintech.com/active-directory-tip-access-external-website-with-the-same-domain-name-as-your-internal-domain/
@abbasiftt, Their malserver is hosted by thirdparty, they are using POP3 through Outlook interface to access their emails...
@ KCTS, I thought I've seen A record of www in the DNS server, I'll check this again I might be mistaken. If not I'll try your suggestion and if doesn't work i'll try the below link also which I just come across just now.
http://oddjobsintech.com/active-directory-tip-access-external-website-with-the-same-domain-name-as-your-internal-domain/
@abbasiftt, Their malserver is hosted by thirdparty, they are using POP3 through Outlook interface to access their emails...
Then you can rename your domain name
The issue for now right now is when you try to resolve the internal domain name using NSLOOKUP, it returns their public ip address...
Do the client use the internal DNS? They should not point to an external DNS on their NIC.
Do the client use the internal DNS? They should not point to an external DNS on their NIC.
ASKER
Few questions about renaming the domain:
If the old DC is shutdown, obvious this has to be done after hour since there will be on users can logon to the domain?
When the DC data are exported and imported into the new DC via "Ideal Administrator" what happened to the SID, encrypted users' password? Will AD objects retain their SID?
Is there a possibility that the import of AD data via "Ideal Administrator" will be unsucessful?
ASKER
.........no users can logon to the domain?
ASKER
@ snusgubben, the option from the DHCP uses the internal DNS ip address provided to the clients.
I don't see why you want to do a domain rename.
It's common to have .com both internal and external, and if you are experiencing any problems why not fix them? :)
It's common to have .com both internal and external, and if you are experiencing any problems why not fix them? :)
ASKER
Experienced tough me often the KISS approach far outweight cumbersome methodology.
What's the KISS approach?
Keep
It
Simply
Stupid.
Thank you all, Appreciate your input.
What's the KISS approach?
Keep
It
Simply
Stupid.
Thank you all, Appreciate your input.