Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

A while back when I first started with my company, the domain had already been set up using a "xxx.net" DNS name for the internal AD namespace. The shortname is just fine and I feel no need to change it but I have always hated how we used an internet DNS name for our internal AD. We are planning an AD upgrade from 2003 to 2008R2 and I would like to work this DNS name change if possible.

I know there are procedures for doing a full domain name change but my question is: Is a FULL domain name change neccessary if all I want to change is the internal DNS name of the domain? Would it be better to do this change after the 2008R2 domain upgrade?

share|improve this question
    
I think you should just make it yyy.xxx.net, where YYY is your internal name as a sub-domain of xxx.net. –  user3914 Feb 4 '11 at 17:58
1  
I would wait for 2008 R2 full functionnal level to get all my chances with me. if you go for a full rename, my experiences: lordoftheping.blogspot.com/2006/07/domain-rename-done.html lordoftheping.blogspot.com/2006/08/… I wouldn't do any of that for a dns name. It's just a name, you should go over the psychological barrier. –  Mathieu Chateau Feb 4 '11 at 19:16

1 Answer 1

up vote 3 down vote accepted

If I were you, I'd just leave it as-is. Split DNS is a perfectly valid infrastructure choice, and in some cases would make life easier when switching between the office and being on the road if that's required.

For example, using split DNS, you could point Outlook to mail.company.net. This would allow you to get your mail internally via MAPI, and via RPC/HTTP or Outlook Anywhere when away from the office - all without having to reconfigure Outlook. The same goes for Exchange 2007/2010 Autodiscover service records - assuming you're using Exchange, that is.

Otherwise, if you want to proceed with the rename, I don't think the functional level of the domain will affect the outcome or execution of the rename process at all. I've done several renames as well as AD migrations at 2003 functional level without issues. I'd do it before the upgrade and make sure everything's bedded down and error-free before moving to a 2008 domain.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.