Consequences of changing primary DNS Suffix

Discussion in 'Windows Server' started by Adam, Feb 6, 2005.

  1. Adam

    Adam Guest

    Dumb question, but I just setup a server and 15 machines. I joined the
    domain, installed exchange 2003 etc, and all the machines are working great.
    However, the current Primary DNS suffix is; whereas, I need it
    to just be Is there a simple way to do this without having to reload
    Windows 2003 and/or rejoin all the workstations? Thanks in advance!!
    Adam, Feb 6, 2005
    1. Advertisements

  2. Adam

    Todd J Heron Guest

    We need more details on your setup. Can you please provide the following

    1) Domain name from Active Directory Users & Computers
    2) List of all Forward Lookup Zones in the DNS console
    3) Output of ipconfig /all from a client and from the DC (an unedited
    version - please do not make any changes)
    Todd J Heron, Feb 6, 2005
    1. Advertisements

  3. Adam

    Adam Guest

    3) everything is listed as Other than the specific IP
    addresses. This server is not a web server, just internal.
    Adam, Feb 6, 2005
  4. Adam

    Todd J Heron Guest

    Ok, thanks. You are going to have to conduct an Active Directory Rename
    procedure. Won't impact you much b/c you only have 15 workstations.

    Windows Server 2003 domain rename procedure.

    Domain rename Web site:

    Implementing an Active Directory Domain Rename Operation:

    Windows Server 2003 Domain Rename Tools:

    Step-by-Step Guide to Implementing Domain Rename:

    Windows Server 2003 Active Directory Domain Rename Tools:

    Renaming a Domain in Windows Server 2003:

    The main points for domain rename are (and thanks to Ulf B. Simon-Weidner
    for help on a lot of these notes):
    - Backup DC(s) first
    - One needs to be running some version of Windows Server 2003 to act as the
    control station, which has to be a member server of the domain.
    - Won't work if Certificate Services is installed in the domain (will have
    to remove and re-install)
    - All DCs need to be Windows Server 2003, andthe Domain and Forest
    functional levels must be set to Windows Server 2003
    - Do not perform forest re-structuring at the same time as the rename (i.e.,
    the number of domains must remain the same - do not add or remove domains
    during this operation (this is a moot point if only single domain)
    - All domain clients and member servers must be restarted twice, and NT 4.0
    systems need to be removed and re-added to the domain
    - There may be applications which need to be adjusted on the clientside to
    the new FQDN (such as Exchange)
    - Use the current domain rename tool available from (avoid the
    one from the CD - notes from this group indicate it has flaws).
    - Read the domain rename guide thouroughly. Read up to and including the
    last page. Many people make the error not finishing the domain rename 100%
    because they think they are finished when the guide talks about specific
    scenarious to take care of. There's more afterwards.
    Todd J Heron, Feb 6, 2005
  5. Adam

    Adam Guest

    Thank you. So just one final question, I should only have to worry about the
    exchange? I do not have to worry about actually re-joining each workstation
    to the domain, correct??
    Adam, Feb 6, 2005
  6. Adam

    Todd J Heron Guest

    Adam>I should only have to worry about the exchange?

    Yes, if you're looking for a one-word answer. But the whole rename
    procedure is not to be taken lightly. Read through the docs before

    Adam>I do not have to worry about actually re-joining each workstation to
    the domain, correct??

    No, provided they are all 2000 or XP.
    Todd J Heron, Feb 6, 2005
    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.