Rename Domain

4 Mar 2006 5:04 AM

Jeff Grossman

I just set up a Domain Controller on Windows Server 2003. I called
the domain domain.com. I have realized that probably was not a great
choice, and want to change it to domain.local. I have about 2 users
using the domain right now. Would it be easier/better for me to try
and rename the domain, or just start over from scratch? If the rename
approach is easier/better, how would I go about doing it? Are there
any step by step instructions?

Thanks,
Jeff

4 Mar 2006 9:11 AM

Norbert Fehlauer [MVP]

Jeff Grossman wrote:
Hi,

> I just set up a Domain Controller on Windows Server 2003. I called
> the domain domain.com. I have realized that probably was not a great
> choice, and want to change it to domain.local.

I would call my domain something.local. Whats wrong with .com?

> I have about 2 users
> using the domain right now. Would it be easier/better for me to try
> and rename the domain, or just start over from scratch?

Starting over from scratch would be the easier way, imho.

> If the rename
> approach is easier/better, how would I go about doing it? Are there
> any step by step instructions?

Just take a look in the MSKB.
http://support.microsoft.com/kb/842116/en-us

HTH
Norbert

--
Dilbert's words of wisdom #19: Am I getting smart with you? How would
you know?

4 Mar 2006 9:50 AM

Norbert Fehlauer [MVP]

Norbert Fehlauer [MVP] wrote:

> I would call my domain something.local.

I meant "I wouldn't" ;)
http://support.microsoft.com/kb/296250/en-us
Three practical methods to name the DNS domain are:
I wouldn't use the first method because there are already known issues with
it.
http://support.microsoft.com/kb/836413/en-us
Also thise is solved easily I would suggest one of the other two methods.

HTH
Norbert

--
Dilbert's words of wisdom #10: I don't have an attitude problem. You
have a perception problem.

4 Mar 2006 10:18 PM

Jeff Grossman

"Norbert Fehlauer [MVP]" <n.fehla***@gmx.net> wrote:

>Norbert Fehlauer [MVP] wrote:
>> I would call my domain something.local.
>
>I meant "I wouldn't" ;)
>http://support.microsoft.com/kb/296250/en-us
>Three practical methods to name the DNS domain are:
>I wouldn't use the first method because there are already known issues with
>it.
>http://support.microsoft.com/kb/836413/en-us
>Also thise is solved easily I would suggest one of the other two methods.

Thank you for this information and the advice in the previous message.
The reason I was thinking of going with a .local extension instead of
a .com is because of the negatives listed in the first link above. I
currently have my website hosted outside our internal network. I have
a local DNS server for internal clients to connect to and I have an
external DNS server set up for external clients. When I put the
active directory system in place and set up the DNS on the AD machine,
it is syncing up with the internal DNS because that is what is
considered authoritative for my domain, internally. But, some of my
clients are no longer able to connect to the outside webpage using
domain.com. They can only connect using www.domain.com. I do not
want to limit that ability.

So, I figured it might be best to go with either domain.local or
ad.domain.com for the AD domain. I am still trying to figure out my
options. But, now after reading the second link, I might have a
problem with the .local method. I am currently an all Macintosh
house, moving to Windows. So, if Macintosh has a problem with .local,
I might want to rethink that method now too.

Thanks for the valuable links and information.

Jeff

4 Mar 2006 11:02 PM

Norbert Fehlauer [MVP]

Jeff Grossman wrote:
Hi,

> or ad.domain.com for the AD domain.

Thats the way I would do it. But it's just one out of three options. ;)

Bye
Norbert

--
Dilbert's words of wisdom #34: When you don't know what to do, walk
fast and look worried.

6 Mar 2006 4:40 PM

Jeff Grossman

"Norbert Fehlauer [MVP]" <n.fehla***@gmx.net> wrote:

>Jeff Grossman wrote:
>Hi,
>
>> or ad.domain.com for the AD domain.
>
>Thats the way I would do it. But it's just one out of three options. ;)
>
>Bye
>Norbert

Thanks for the valuable information you have supplied. I will think
about which solution would benefit my organization the best.

Jeff

5 Mar 2006 10:24 PM

Cary Shultz

Jeff,

There is an extremely easy solution for getting to http://www.domain.com...

Create a www record in your Forward Lookup Zone and give it the public IP
Address of your web site.

It is really that simple!

--
Cary W. Shultz
Roanoke, VA 24012

Show quoteHide quote

"Jeff Grossman" <jeff.nospam@stikman.com> wrote in message
news:j94k02tkjofn467a0smpkc1qro5gek01jr@4ax.com...
> "Norbert Fehlauer [MVP]" <n.fehla***@gmx.net> wrote:
>
>>Norbert Fehlauer [MVP] wrote:
>>> I would call my domain something.local.
>>
>>I meant "I wouldn't" ;)
>>http://support.microsoft.com/kb/296250/en-us
>>Three practical methods to name the DNS domain are:
>>I wouldn't use the first method because there are already known issues
>>with
>>it.
>>http://support.microsoft.com/kb/836413/en-us
>>Also thise is solved easily I would suggest one of the other two methods.
>
> Thank you for this information and the advice in the previous message.
> The reason I was thinking of going with a .local extension instead of
> a .com is because of the negatives listed in the first link above. I
> currently have my website hosted outside our internal network. I have
> a local DNS server for internal clients to connect to and I have an
> external DNS server set up for external clients. When I put the
> active directory system in place and set up the DNS on the AD machine,
> it is syncing up with the internal DNS because that is what is
> considered authoritative for my domain, internally. But, some of my
> clients are no longer able to connect to the outside webpage using
> domain.com. They can only connect using www.domain.com. I do not
> want to limit that ability.
>
> So, I figured it might be best to go with either domain.local or
> ad.domain.com for the AD domain. I am still trying to figure out my
> options. But, now after reading the second link, I might have a
> problem with the .local method. I am currently an all Macintosh
> house, moving to Windows. So, if Macintosh has a problem with .local,
> I might want to rethink that method now too.
>
> Thanks for the valuable links and information.
>
> Jeff

5 Mar 2006 10:51 PM

Norbert Fehlauer [MVP]

Cary Shultz wrote:
Hi,

> It is really that simple!

Yes it's that simple, but the OP meant something different:

> But, some of my
> clients are no longer able to connect to the outside webpage using
> domain.com. They can only connect using www.domain.com.

Bye
Norbert

6 Mar 2006 4:39 PM

Jeff Grossman

"Cary Shultz" <cwshu***@mvps.org> wrote:

>Jeff,
>
>There is an extremely easy solution for getting to http://www.domain.com...
>
>Create a www record in your Forward Lookup Zone and give it the public IP
>Address of your web site.
>
>It is really that simple!

Yes, I know. But, I also want my internal machines to be able to use
domain.com to get to the website. Which, if that is the name of the
domain in AD, it is not possible.

Jeff

8 Mar 2006 6:57 AM

MichaelHensley

Our domain name is "example.com", and our web site, which is hosted
externally, is www.example.com. Our internal users have no problem accessing
it. I added a type "A" record to our internal DNS server pointing at the
external IP address of "www".

The only problem we have is if an internal users tries to access a page at
www.example.com/dirname (without the trailing slash), the get an error.
Using www.example.com/dirname/ works, so we just make sure all links which
point to directories have a trailing slash.

Show quoteHide quote

"Jeff Grossman" <jeff.nospam@stikman.com> wrote in message
news:mcpo021fps84hrab778h1k5pm5vvvcg1ud@4ax.com...
> "Cary Shultz" <cwshu***@mvps.org> wrote:
>
>>Jeff,
>>
>>There is an extremely easy solution for getting to
>>http://www.domain.com...
>>
>>Create a www record in your Forward Lookup Zone and give it the public IP
>>Address of your web site.
>>
>>It is really that simple!
>
> Yes, I know. But, I also want my internal machines to be able to use
> domain.com to get to the website. Which, if that is the name of the
> domain in AD, it is not possible.
>
> Jeff