Single Label domain limitation

[Chris Dahl]

IS there any reason that a Win2003 and Exchange 2003 combination will not
work with a single label domain configuration.

We currently have four areas. One (8000 users) of which is running in
Windows 2000 native mode with a single label

domain as the root, a single child domain and Exchange 5.5. The plan is to
bring three other areas (25000 users) as

three additional child domains and also upgrade all areas to Win2003 and
Ex2003.

We (the other three areas) have already realized that the single label
domain may be a problem after installing W2K with

SP4 and are looking at possible problems in the future. As we do not have a
great investment in W2K at this point it is

the belief that creating a new forest using a supported naming structure and
merging the existing single area into the

new forest would make more sense. The other idea is to continue as we are
and do a rename after all areas are brought

up.

Is there any compelling reason for either choice?

Thanks

Chris Dahl

I understand that my posting to this many graoups may not be proper but I am
attempting to get a much information as possible in the short amount of time
I have been given to research this.

 

[Danny Sanders]

Here is a post for Alan Wood from MS:

"We really would preffer to use FQDN over Single labled. There are
alot of other issues that you can run into when using a Single labeled
domain name with other AD integrated products. Exchange would be a great
example. Also note that the DNR (DNS RESOLVER) was and is designed to
Devolve DNS requests to the LAST 2 names.

Example: Single Labeled domain .domainA
then, you add additional domains on the forest.
child1.domainA
Child2.child1.domainA

If a client in the domain Child2 wants to resolve a name in domainA
Example. Host.DomainA and uses the following to connect to a share
\\host then it is not going to resolve. WHY, because the resolver is
first going to query for first for Host.Child2.child1.domainA, then it
next try HOST.Child1.domainA at that point the Devolution process is
DONE. We only go to the LAST 2 Domain Names.

Also note that if you have a single labeled domain name it causes excess
DNS traffic on the ROOT HINTS servers and being all Good Internet Community
users we definitely do not want to do that. NOTE that in Windows 2003,
you get a big Pop UP Error Message when trying to create a single labeled
name telling you DON'T DO IT. It will still allow you to do it, but you
will still be required to make the registry changes, which is really not
fun.

Microsoft is seriously asking you to NOT do this. We will support you but
it the end results could be limiting as an end results depending on the
services you are using.


Thank you,

Alan Wood[MSFT]"





I would suggest getting rid of the single label domain NOW rather than
later. You will run into issues you don't need to if you leave it single
label and try to upgrade to Win 2k3 and Exchange 2k3.



hth

DDS W 2k MVP MCSE

 

[Kirill S. Palagin]

AFAIK, W2K3 allows you to rename domain so you may consider that as an
option.

 

[Rich Matheisen [MVP]]

AFAIK, W2K3 allows you to rename domain so you may consider that as an
option.

not if there's exchange anywhere in the forest!

 

[Kirill S. Palagin]

not if there's exchange anywhere in the forest!

Exchange as in "Exchange 2000" or "Exchange 2003"?

 

[Russ Kaufmann]

Exchange as in "Exchange 2000" or "Exchange 2003"?

Either.

 

[Kirill S. Palagin]

Either.

So original poster needs to rename domain first and only then introduce
E2K3.

 

[Rich Matheisen [MVP]]

[ snip ]

Exchange as in "Exchange 2000" or "Exchange 2003"?

take your pick.

 

[Rich Matheisen [MVP]]

[ snip ]

So original poster needs to rename domain first and only then introduce
E2K3.

yes. or just give up on the whole idea.

 

[Guest]

Thanks to all

This basically confirms what we already suspected.

Chris Dahl