Renaming the Domain

Discussion in 'Server Networking' started by pestocat, Feb 7, 2006.

  1. pestocat

    pestocat Guest

    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
     
    pestocat, Feb 7, 2006
    #1
    1. Advertisements

  2. In
    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.
     
    Lanwench [MVP - Exchange], Feb 7, 2006
    #2
    1. Advertisements

  3. pestocat

    pestocat Guest

    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]"
     
    pestocat, Feb 7, 2006
    #3
  4. pestocat

    Bill Grant Guest

    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.
     
    Bill Grant, Feb 7, 2006
    #4
  5. pestocat

    pestocat Guest

    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.
     
    pestocat, Feb 7, 2006
    #5
  6. 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/You_Need_to_Create_a_Split_DNS.html


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

    Microsoft Internet Security & Acceleration Server: Guidance
    http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
    http://www.microsoft.com/isaserver/techinfo/Guidance/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/prodtechnol/isa/2004/deploy/dgisaserver.mspx
    -----------------------------------------------------
     
    Phillip Windell, Feb 7, 2006
    #6
  7. 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/ISA2004_AccessRules.html

    Microsoft Internet Security & Acceleration Server: Guidance
    http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
    http://www.microsoft.com/isaserver/techinfo/Guidance/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/prodtechnol/isa/2004/deploy/dgisaserver.mspx
     
    Phillip Windell, Feb 7, 2006
    #7
  8. pestocat

    pestocat Guest

    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


     
    pestocat, Feb 7, 2006
    #8
  9. 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/ISA2004_AccessRules.html

    Microsoft Internet Security & Acceleration Server: Guidance
    http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
    http://www.microsoft.com/isaserver/techinfo/Guidance/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/prodtechnol/isa/2004/deploy/dgisaserver.mspx
    -----------------------------------------------------
     
    Phillip Windell, Feb 7, 2006
    #9
  10. pestocat

    krag Guest

    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?
     
    krag, Feb 9, 2006
    #10
  11. In
    Phil already mentioned this, but there is absolutely no reason you can't run
    a mail and web server with your existing AD domain name. None.




     
    Lanwench [MVP - Exchange], Feb 9, 2006
    #11
  12. There is no such thing as a routable FQDN,...they are just names,...they
    don't go anywhere. There is absolutely no relationship between your Active
    Directory FQDN and the Publicly Registered FQDN,...they serve two different
    purposes in two differnt "worlds". The only thing they have in common is
    that they both use "Dot Notation" and they can both be refered to as a
    FQDN,...which just simply refers to the fact that they use "dot notation".

    Your Internal AD FQDN could be "myself.lost.chicken.soup.local" while your
    email addresses and your Public FQDN can be "mycompany.com", there is simply
    no connection between the two.

    I took that much time to explain that because it is very important to
    understand that. People create all kinds of disasters for themselves
    because they don't understand that.

    As far as Renaming, it can be done if it is a Server2003 Domain and you have
    not yet installed Exchange or any other product that alters the AD Schema.
    Once Exchange is installed, the AD Schema is altered and it becomes
    permanet. I have heard of third party utilities that can overcome this, but
    I don't know if I would trust them. The proper way to rename after Exchange
    would be to create a whole New Domain / New Forest with the right name.
    Create a Trust between it and the old Domain,..then use the Active Directory
    Migration Tool (ADMT) and "migrate" everything to the New Domain then break
    the trust and eliminate the old domain. They have nice, big, long, White
    Papers to read for that ;-)

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

    Microsoft Internet Security & Acceleration Server: Guidance
    http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
    http://www.microsoft.com/isaserver/techinfo/Guidance/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/prodtechnol/isa/2004/deploy/dgisaserver.mspx
    -----------------------------------------------------
     
    Phillip Windell, Feb 10, 2006
    #12
  13. pestocat

    pestocat Guest

    Phillip,
    I read some more documents and finally found the right one. I kept the
    domain name as is and after about 5 minutes of configuration changes to both
    the AD server and the client, all is well. I don't loose connection to the
    printer and to shared files. Thanks for all the assistance
    pestocat



     
    pestocat, Feb 14, 2006
    #13
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.