Naming a Domain

[Robert J]

I am setting up my first Win2K Server and it is going to be a domain
controller for a small company with 5 users.

They have a registered domain name that is very long. I would like the
company to register a similar but shorter name. The new name is available.

If I put the new name in when setting up the domain controller (prior to
registering) is that going to mess up anything? I want to name the domain
the same as the registered name. Would it be wierd or cause any problems to
have the names be the same, so the active directory name would be
THISCOMPANY.THISCOMPANY.COM?

Also, what do you think about just naming the server SERVER? This is a very
small company that will never have more than one server

 

[Brian Desmond [MVP]]

You can use mycompany.com if you like. I'd recommend you consider setting
something like ad.company.com up so your public and internal DNS namespaces
aren't on the same DNS. This isn't an issue if you do split DNS, though
(split DNS is where you host your external DNS on seperate servers which
don't communicate with the AD).

Naming the server SERVER is fine.

--
--
Brian Desmond
Windows Server MVP
(e-mail address removed)12.il.us

Http://www.briandesmond.com

 

[Brian Kronberg]

Even better; use a non-existant Top Level Domain (TLD)
like .local or .internal. Using anything .com or .net
could possible cause DNS conflicts therefore make life
easier on yourself and pick an easier internal name and
TLD.

Example (made up company name):
external site: DistributedSalesNetwork.com
internal site: dsn.local

Brian Kronberg
CNE, MCSA, and more
(no $ in my email)