Windows 2000 Active Directory domain names

Posted on 2003-03-29
Medium Priority
Last Modified: 2010-04-13

Currently have Win2k with the root domain as mycorp.com and one sub-domain of us.mycorp.com.  Now the company changed names about a year ago and we want the domain name to reflect that change.  We decided against waiting for Windows 2003 to come out and change it, for various reasons I won't get into.  Instead we are going to create an entirely new tree, with the root domain as newcorpname.com and sub-domains for each geographic area us.newcorpname.com, uk.newcorpname.com, ca.newcorpname.com, etc.  Then create a trust between newcorpname.com and mycorp.com and gradually move everything over and finally get rid of the old domain tree.  The problem that someone brought up is that we can't have two domains with the same name (ie "us"), now technically the domain name is us.newcorpname.com and us.mycorp.com, but you really only see the "us" part in the domain.  For instance during logon from a workstation the domain field just reads "us".  When we setup the trust how are you suppose to differentiate between the two domains, can we?


Question by:jvieira
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
LVL 10

Accepted Solution

ryangorman earned 500 total points
ID: 8234866
DNS domain names must be unique within an organisation. This is the case with 'us.newcorpname.com' and 'us.mycorp.com'.

NETBIOS names must be unique within an organisation...
This would be the case where the NETBIOS name for 'us.newcorpname.com' is 'US' and the NETBIOS name for 'us.mycorp.com' is 'USMYCORP'.

My feeling would be to re-think the desire/need to base the *internal* Windows 2000 domain name (i.e.  the infrastructure) on the *current* trading name of your company.

Author Comment

ID: 8235267
Why would 'us.newcorpname.com' be 'US' and 'us.mycorp.com'
be 'USMYCORP' (no period between us and mycorp).

Basing the domain name on the company was a business decision.  Considering we have changed our names 5 times in six years, you would think that it would be a bad decision.  But management wants to show our parent company (who just bought us) that we aren't going anywhere.  Next year when we change our name again, I'll be posting a question about using Win 2003 to change domain names.
LVL 10

Expert Comment

ID: 8237239
>>Why would 'us.newcorpname.com' be 'US' and 'us.mycorp.com' be 'USMYCORP' (no period between us and mycorp).

This was in response to your question 'is their a conflict if two different W2K domains share the same third level domain name'. I am saying that there is no conflict of DNS names but you must remember to keep the NETBIOS names unique.

I'm glad that you recoqnise that basing the W2K domain name on the current business name makes a rod for own back. The *internal* DNS domain name has virtually no bearing on the available choices for the external domain names (WWW, email etc.)


Author Comment

ID: 8265369
>>This was in response to your question 'is their a >>conflict if two different W2K domains share the same >>third level domain name'. I am saying that there is no >>conflict of DNS names but you must remember to keep the >>NETBIOS names unique.

Sorry, I misread the original posting, which is why asked that question.  After further debate the company has decide for the US, the domain name will be USA.newcorpname.com and the rest of the domains will use two letters (CA - Canada, AU - Australia, etc...).  If you think this idea is really stupid try this.

The domain names is actually  USA.companynameinitials.parentcompanyname.com
example Acme owns Micro Products.  the domain name is usa.mp.acme.com which is only the internal DNS domain name.  No one outside Acme or Micro Products can look up these dns entries.  Our external domain name is microproducts.com

So if we are keeping to seperate dns domain names why base the internal one on the company name which might change sometime in the near future (and cause my brain to explode when they ask me to change it)?  I really think they're are doing it just to make my life hell.
LVL 10

Expert Comment

ID: 8268383
I've done a few Windows 2000 Active Directory deployments and spent some time thinking about AD forest root DNS names. I've come to the conclusion that the internal DNS name should not be tied to the current company trading name. After all, its an internal 'infrastructure' name barely seen by internal users.

Its promised that Windows 2003 and later support namespace renaming. I say good, but with prior planning we can avoid the extra work that renaming would involve.

You're right though, they're only doing it to make your life hell.

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
Ready to get certified? Check out some courses that help you prepare for third-party exams.
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
This tutorial will teach you the special effect of super speed similar to the fictional character Wally West aka "The Flash" After Shake : http://www.videocopilot.net/presets/after_shake/ All lightning effects with instructions : http://www.mediaf…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question