Tweet
When setting up a domain controller, do you require a TLD for all hosts?
For example, I have the server environment setup with the following internal TLD's.
www01.vertical.prod
www01.vertical.stg
www01.vertical.qa
www01.vertical.dev
lb01.network.ops
etc.etc.etc.
I want to get rid of linux ldap and just use Windows LDAP to consolidate the protocol. However I am being told that Windows AD needs all of the above hosts to be apart of a primary domain, which will end up making things messy and redundant. ( eg. www01.vertical.prod.company.com )
.
I do not want to tie the application platforms to a company related domain name incase any of the vertical markets are sold as its a pain in the ass to unattached it from a primary TLD across the farm ( updating host records, adjusting configuration files, etc.... )
What I would like to do, is just have the Windows AD controller handle requests for all of the above TLD's without having to tie them all together with a domain name. Possible?
Thanks.
For example, I have the server environment setup with the following internal TLD's.
www01.vertical.prod
www01.vertical.stg
www01.vertical.qa
www01.vertical.dev
lb01.network.ops
etc.etc.etc.
I want to get rid of linux ldap and just use Windows LDAP to consolidate the protocol. However I am being told that Windows AD needs all of the above hosts to be apart of a primary domain, which will end up making things messy and redundant. ( eg. www01.vertical.prod.company.com )
.
I do not want to tie the application platforms to a company related domain name incase any of the vertical markets are sold as its a pain in the ass to unattached it from a primary TLD across the farm ( updating host records, adjusting configuration files, etc.... )
What I would like to do, is just have the Windows AD controller handle requests for all of the above TLD's without having to tie them all together with a domain name. Possible?
Thanks.