Renaming the Domain

I want to rename my internal domain. The application rendom.exe is used to
accommodate the change. But from the step by step instructions, it seems
that I must have another computer running Win Server 2003 that is used to
send the commands. I can't use the domain controller. I don't have another
PC with Win Server 2003. I think it would be easier just to delete my domain
and start over again. Is this the way it's done.
pestocat

In news:(E-Mail Removed),
pestocat <(E-Mail Removed)> typed:
> I want to rename my internal domain. The application rendom.exe is
> used to accommodate the change. But from the step by step
> instructions, it seems that I must have another computer running Win
> Server 2003 that is used to send the commands. I can't use the domain
> controller. I don't have another PC with Win Server 2003. I think it
> would be easier just to delete my domain and start over again. Is
> this the way it's done. pestocat

What's the impetus behind your desire to rename the domain in the first
place? Who besides you & your internal users will ever see it? Is it named
something vulgar?

That said - see if http://www.msexchange.org/tutorials/Domain-Rename.html
helps.

I need to get DNS to work like it is suppose to. I need to rename x.local to
x.y.com in order to follow the normal process. x is private, y.com is
public.



"Lanwench [MVP - Exchange]"
<(E-Mail Removed) ahoo.com> wrote in message
news:(E-Mail Removed)...
>
>
> In news:(E-Mail Removed),
> pestocat <(E-Mail Removed)> typed:
>> I want to rename my internal domain. The application rendom.exe is
>> used to accommodate the change. But from the step by step
>> instructions, it seems that I must have another computer running Win
>> Server 2003 that is used to send the commands. I can't use the domain
>> controller. I don't have another PC with Win Server 2003. I think it
>> would be easier just to delete my domain and start over again. Is
>> this the way it's done. pestocat
>
> What's the impetus behind your desire to rename the domain in the first
> place? Who besides you & your internal users will ever see it? Is it named
> something vulgar?
>
> That said - see if http://www.msexchange.org/tutorials/Domain-Rename.html
> helps.
>

I am not sure what you mean by "get DNS to work as it is supposed to". DNS
can work quite happily with the internal and external names being the same
as each other or completely different. Renaming your domain doesn't seem to
me the logical way to solve your DNS problems.

I would like the domain to be as recommended by Microsoft in their document
"DNS Step-by-Step Guide". It seems to be a cleaner design than the one I
have now, whose name is x.local. I want to rename it x.y.com, where y.com is
the public domain.



"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
> I am not sure what you mean by "get DNS to work as it is supposed to".
> DNS can work quite happily with the internal and external names being the
> same as each other or completely different. Renaming your domain doesn't
> seem to me the logical way to solve your DNS problems.
>

"pestocat" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> I need to get DNS to work like it is suppose to. I need to rename x.local
to
> x.y.com in order to follow the normal process. x is private, y.com is
> public.

No that isn't what you should do. Internal and External Domain namse should
be different. I always use the same primary name but chance the TLD for the
Internal to "*.loc" (keep it three letters, some OS's have a fit with more
than that, like "*.local").

If you do make both intenral andexternal the same then you need to create a
complex Split-DNS setup that requires two DNS Servers. There are ways to
get around that without Split-DNS but it is messy. It is better to avoid the
whole issue and leave the name internal vs external names different. They
each serve an entirely different purpose anyway, so they logically should be
different names.

Here's the Split-DNS article if you want it:

[Those are underscores, not spaces between the words]
You Need to Create a Split DNS!
http://www.isaserver.org/tutorials/Y...Split_DNS.html


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/pro...isaserver.mspx
-----------------------------------------------------

Don't bother. It sounds bad,...but in some cases,..those documents are the
opinion of the one particular individual who wrote it,...and arguably they
may not always be right or may not always present the best way. You can
probably find an equal number, if not more, documents that tell you to keep
the names different.


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/pro...isaserver.mspx
-----------------------------------------------------



"pestocat" <(E-Mail Removed)> wrote in message
news:%23w9zp6$(E-Mail Removed)...
> I would like the domain to be as recommended by Microsoft in their
document
> "DNS Step-by-Step Guide". It seems to be a cleaner design than the one I
> have now, whose name is x.local. I want to rename it x.y.com, where y.com
is
> the public domain.
>
>
>
> "Bill Grant" <not.available@online> wrote in message
> news:(E-Mail Removed)...
> > I am not sure what you mean by "get DNS to work as it is supposed to".
> > DNS can work quite happily with the internal and external names being
the
> > same as each other or completely different. Renaming your domain doesn't
> > seem to me the logical way to solve your DNS problems.
> >
>
>

Phillip,
Thank you all for the good info and feedback. The x.local domain is very
simple with just 4 clients. The y.com DNS is handled at my ISP. For right
now I will keep it as is. The problem that I'm having is that I loose
connection to network printer and shared files after several hours. I need
to reboot the client to get the printer connection again. However, pinging
the server and clients works OK.
Thanks


"Phillip Windell" <@.> wrote in message
news:eAd%23v%23$(E-Mail Removed)...
> "pestocat" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> I need to get DNS to work like it is suppose to. I need to rename x.local
> to
>> x.y.com in order to follow the normal process. x is private, y.com is
>> public.
>
> No that isn't what you should do. Internal and External Domain namse
> should
> be different. I always use the same primary name but chance the TLD for
> the
> Internal to "*.loc" (keep it three letters, some OS's have a fit with
> more
> than that, like "*.local").
>
> If you do make both intenral andexternal the same then you need to create
> a
> complex Split-DNS setup that requires two DNS Servers. There are ways to
> get around that without Split-DNS but it is messy. It is better to avoid
> the
> whole issue and leave the name internal vs external names different. They
> each serve an entirely different purpose anyway, so they logically should
> be
> different names.
>
> Here's the Split-DNS article if you want it:
>
> [Those are underscores, not spaces between the words]
> You Need to Create a Split DNS!
> http://www.isaserver.org/tutorials/Y...Split_DNS.html
>
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
>
> Deployment Guidelines for ISA Server 2004 Enterprise Edition
> http://www.microsoft.com/technet/pro...isaserver.mspx
> -----------------------------------------------------
>
>
>

"pestocat" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Phillip,
> Thank you all for the good info and feedback. The x.local domain is very
> simple with just 4 clients. The y.com DNS is handled at my ISP. For right
> now I will keep it as is. The problem that I'm having is that I loose
> connection to network printer and shared files after several hours. I need
> to reboot the client to get the printer connection again. However, pinging
> the server and clients works OK.

That problem doesn't have anything to do with the Doamin Name. But with
such a small system you could eliminate the Domain and recreate (and forget
renaming) it with "*.loc" instead of "*.local". Macs and some flavors of
Unix don't work with a 5-letter TLD,..stay with 3 letters and "*.loc" is
probably the best most universal choice. The first part of the name can be
the same as the external one.

Internal = mycompany.loc
External = mycompany.com

The "logic" of the domain names are:

"hostname.domainname.topleveldomain"
serv01 . mycompany . loc (internal example)
www . mycompany . com (enternal example)

If the system is complex with child domains (sub domains) then it would be
like this below, but this is pretty much an internal thing.

""hostname.subdomain.domainname.topleveldomain ""
serv01 . salesdept . mycompany . loc


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/pro...isaserver.mspx
-----------------------------------------------------

My internal domain has the .local extension. I have a static IP and a FQDN.
I would like to change the internal domain name to the routable or FQDN so
that I can run a mail/web server. I presume that this would be simpler than
creating a sub-domain and so on? How do you recommend I o this?
"Phillip Windell" wrote:

> "pestocat" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > Phillip,
> > Thank you all for the good info and feedback. The x.local domain is very
> > simple with just 4 clients. The y.com DNS is handled at my ISP. For right
> > now I will keep it as is. The problem that I'm having is that I loose
> > connection to network printer and shared files after several hours. I need
> > to reboot the client to get the printer connection again. However, pinging
> > the server and clients works OK.
>
> That problem doesn't have anything to do with the Doamin Name. But with
> such a small system you could eliminate the Domain and recreate (and forget
> renaming) it with "*.loc" instead of "*.local". Macs and some flavors of
> Unix don't work with a 5-letter TLD,..stay with 3 letters and "*.loc" is
> probably the best most universal choice. The first part of the name can be
> the same as the external one.
>
> Internal = mycompany.loc
> External = mycompany.com
>
> The "logic" of the domain names are:
>
> "hostname.domainname.topleveldomain"
> serv01 . mycompany . loc (internal example)
> www . mycompany . com (enternal example)
>
> If the system is complex with child domains (sub domains) then it would be
> like this below, but this is pretty much an internal thing.
>
> ""hostname.subdomain.domainname.topleveldomain ""
> serv01 . salesdept . mycompany . loc
>
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
>
> Deployment Guidelines for ISA Server 2004 Enterprise Edition
> http://www.microsoft.com/technet/pro...isaserver.mspx
> -----------------------------------------------------
>
>
>
>