Re: subdomain namespace question

From: Joe Richards [MVP] (humorexpress_at_hotmail.com)
Date: 01/08/05 

Date: Fri, 07 Jan 2005 21:57:44 -0500

This is absolutely fine and called a disjoint namespace and is fully supported.
It is very common in very large enterprise customers because they don't want to
say use one namespace for some hundred thousand machines across the US and
instead break it up geographically by city or region but have a single AD
domain. So for instance you could have a machine with a name of
joeuser1.west.company.com in an AD domain of company.com.

There is a KB article on setting some specific permissions for machines this is
done with so they can properly configure their spns and hostnames in AD.

I was actually with a Global 5 company back in April 2000 when we brought this
up to MS and got a definitive answer that this is and will be fully supported.

Note however that some third party (and even some MS add on apps) will screw up
with disjoint namespaces due to poor programming and shitty testing on the part
of the vendor.

   joe 

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net
Keith Ng wrote:
> Hi all,
> 
> We are designing a new namespace for our new AD (2003 servers). We have an
> Unix based DNS server (BIND) for name resolution. We are planing to use a
> subdomain name of our root domain to be the namespace for the new AD e.g.
> windows.myroot.com. Since all the Windows clients and servers (soon to be
> domain controllers or member servers) are registered under the root domain,
> e.g. winsrv01.myroot.com, will there be any potential problem with name
> resolution both internally (within the LAN) and externally (VPN access from
> the Internet)?
> 
> Thanks
> 
> Keith
> 
>