Link to home
Start Free TrialLog in
Avatar of PerimeterIT
PerimeterIT

asked on

Upgrading single level Domain

previous network administrator apparently made an error when upgrading our NT4 domain to server 2000 naming our domain:

Company
as opposed to:
Company.local
or
Site1.Company

Now this has suddenly become a major problem because today I was tasked with installing and configuring a new sharepoint install for our company and to my horror I read the requirements that explicitly forbids the use of a single level domain name.


We are currently running a server 2003 domain at the 2003 functional level.

Does anyone know or have experience with correcting this problem?

What are the best practices for naming a company domain? We currently have a parent company with several subsidiaries besides us and the option of trusting domains has come up so I would like to prepare for this eventually if required.
ASKER CERTIFIED SOLUTION
Avatar of Adam Brown
Adam Brown
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I've also taken to using .ad. Cause it's short.
Um...

.ad is Andorra, be sure you own the domain name, do not use it unless you do because if you ever come to trying to get a certificate including that name you'll be in trouble (a public CA will not issue it unless you can prove ownership).

Chris
Seriously? Did not know that. Eh. I've only used it on test networks, so no biggy :D

Phew :) It's on the root zone database list, check out .int in there. .ad is a pain, but nothing compared to .int ;)

Chris