Windows 2000 Active Directory domain names

Hello,

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?

Thanks,

Joe
jvieiraAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ryangormanCommented:
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jvieiraAuthor Commented:
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.
0
ryangormanCommented:
>>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.)

0
jvieiraAuthor Commented:
>>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.
0
ryangormanCommented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.