Posted on 2007-11-23
Right basically I have a Windows 2003 server Standard Edition running company.com as a domain controller, DNS, DHCP (192.168.0.X), SQL, Exchange 2003. I know SQL and exchange is not a good practise, but there we are.
So now, I'm getting another server today at the company.com location to set it up, once its setup it will be moved to its hotel. Now company.com is a name front of several hotels. What we aim to do is have hotel1.company.com, hotel2.company.com etc as child domains under company.com.
We plan to keep 3 servers in a datacentre with MPLS lines going to the hotels. What we intend to do is have 1 server as company.com and the other 2 will be the hotel software and database's.
Now we can also have companyhotels.com as a new domain leaving company.com isolated as the head quarters. But we dont want this, as company.com owns companyhotels.com and the hotels beneath them. e.g. hotel1.companyhotels.com etc.
So were looking for a way to structure this appropriately.