Our very small company is leasing a dedicated Windows 2008 R2 server from Hostgator. We host ASP.NET websites there and I have also set up RDS Remote Apps. I have come to discover that I must have AD installed on that server to properly secure RDS and server resources. I am not allowed to use Local Users or Local Policy to configure RDS...because MS has designed it that way. The server is standalone and there will not be any other domain members.
The server also serves as a registered Private Name Server which I use to configure Website domains. I will use the name nameserver.net as the example. My first inclination was to use a .local extension for my AD domain. But I do not want to mess up the
configuration of the Name Server. The server name is currently srv1.nameserver.net. That same name is used for the SSL certificates and RDS users can point to it to connect via the internet.
I do not know if an AD domain that is different that the publicly registered Nameserver domain can reside on the machine.
I have read that a new "standard" practice is to use subdomain naming...such as ad.nameserver.net. That is what I am leaning toward right now.
Does anyone see a problem with going that route? What shall be wary of?
Thanks for any input.
