Questions

Misnamed Active Directory Forest

+
0 Votes
Locked

Misnamed Active Directory Forest

jbrunsting
Hello, all. I have inherited an Active Directory network that was put together by someone who didn't know entirely what they were doing.

First of all, the setup: my company has a hosted website (we'll call it www.company.com). Now, when they then set up their internal Active Directory forest and domain, they named it company.company.com. Urg.

I had to put in some custom DNS on the DNS servers so that we who are on the company network would still be able to see the website.

Now my question is this: should I try to recreate or move this domain? company.company.com seems pretty clunky and, as you see with the DNS entries, I need to put some custom patches in place. Should I try to rebuild the whole thing? Maybe I should create a new forest like company.local and migrate everyone over to it (should be fun since we also have an Exchange server), or maybe it would be enough to create a new domain of company.local and slowly move everyone off the company.company.com domain, though the the root forest domain would still be company.company.com.

I've never run across a situation like this before, nor have I heard of anything like this before, so I'd really appreciate some opinions on this. I'm an IT staff of just one and I have no other techs here to bounce the ideas off of, so please chime in! Thanks.