We will be transitioning the existing network over from our "sister" company to a brand new network from scratch. If our primary name will be "company," what are company.com, ftp.company, mail.company, and database.company? Would that make "company" the domain/root forest, and all the others sub domains, or trees or something? What's the deal on proper set up?
Please Help!! Thanks :)
2006-12-15 07:26:38 · 3 answers · asked by mlinnj 1 in Computers & Internet ➔ Computer Networking
Set up an AD DNS domain name that is NOT valid on the Internet. Company.local or Company.priv or something like that. The reason for that is that if you use Company.com and mess up your DNS server configuration you will leak your internal AD configuration onto the public Internet. Bad move!
Don't confuse your AD DNS with any DNS namespace that you use on the public internet. Assuming that you are a small outfit, a single domain AD forest will be sufficient.
I get the distinct impression that you are new to AD and networking. I'd STRONGLY suggest that you retain a consultant to assist with the initial design and rollout of your AD infrastructure. If you get it wrong from the beginning, you WILL regret it!
Here are just a few things that are commonly messed up and may be difficult to fix once you're up and running.
1. Single label domain name. DCPROMO will allow you to use an AD DNS name of "company" but you will regret this decision. If you subsequently install Exchange Server, it will give you fits with that configuration.
2. Using a TLD that is valid on the public Internet. As mentioned earlier, this can expose your AD structure to the world.
3. Alowing a '.' (that's a "dot") root in your DNS. That's OK if you will NEVER connect to the internet. If you do, it prevents the use of forwarders on your DNS servers and makes external name resolution a nightmare.
4. Configuring child domains without setting up delegation records on the forest root. If you set up your forest with company.priv at the root and later decide to set up a child domain called west.company.priv you must set up delegation records at the forest root BEFORE installing the first DC in the new domain. If you don't do this properly (it's counter-intuitive) you'll have all sorts of name resolution and service location issues until you fix it.
Get a good consultant to help with your initial setup. Or take some classes on designing and implementing an Active Directory infrastructure.
It's far too complex to cover in any more detail here. And I don't give out my consulting services for free. ;)
2006-12-15 08:45:22 · answer #1 · answered by Bostonian In MO 7 · 0⤊ 0⤋
When you install Active Directory on the first server and it is promoted to a Domain Controller, during the setup you will provide a domain name. As you add each additional member server it will use its local host name, ie M1FTP (member 1 ftp) and make its FQDN (fully qualified domain name) ie. M1FTP.domain.com. All of these machines are part of the same domain within the root of the forest. An example of a child domain would be USA.domain.com or Canada.domain.com with their own individual infrastructure.
2006-12-15 08:41:34 · answer #2 · answered by bscottyd 3 · 0⤊ 0⤋
confident , you may Run 2003 sbs with out area. with out setting up advert(energetic itemizing ) 2003 sbs is quicker than the different abode windows And maximum mandatory element is 2003 Sbs is stabel abode windows This my attitude thank you
2016-10-05 08:55:05 · answer #3 · answered by ? 4 · 0⤊ 0⤋