transfer DNS

Discussion in 'DNS Server' started by Peter Hatzis, Aug 4, 2009.

  1. Peter Hatzis

    Peter Hatzis Guest

    Hello. I have two Win 2003 server. One of them is also DNS server (Active
    intergrated zone). I want to transfer the DNS service to the other server.
    Any instructions?

    Regards, Peter
     
    Peter Hatzis, Aug 4, 2009
    #1
    1. Advertisements


  2. If both servers are domain controllers of the same domain, simply install
    DNS on the other domain controller and the zone will automatically appear
    within 30 minutes. Then uninstall (do not delete the zone) on the original
    domain controller.

    If the other server is not a domain controller, allow zone transfers in the
    source zone, and create a secondary on the non-domain controller, allow
    transfer, then change it to a Primary.

    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and
    confers no rights.

    Please reply back to the newsgroup or forum to benefit from collaboration
    among responding engineers, and to help others benefit from your resolution.

    Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
    Microsoft Certified Trainer

    For urgent issues, please contact Microsoft PSS directly. Please check
    http://support.microsoft.com for regional support phone numbers.
     
    Ace Fekay [MCT], Aug 4, 2009
    #2
    1. Advertisements

  3. Peter Hatzis

    Peter Hatzis Guest

    Hello Ace, thanks for replying. Both servers are domain controllers of the
    same domain. So, the zone will appear automatically in 30 minutes, and then
    change clients DNS settings and that's all?
    The server running DNS now is also an Exchange server. Will be affected if i
    transfer DNS service to the other server? Of course i will change DNS
    setting to point to the new DNS server.

    Regards, Peter
     
    Peter Hatzis, Aug 4, 2009
    #3
  4. Ace,
    I thought it had to be AD integrated for it to work as described. That is a
    nice trick.

    Peter,
    Change the current dc to the new dns server, but if you have only one dns
    server in your domain I would recommend leaving them both up as dns servers.
    Otherwise, even though you are fault tolerant on AD, your clients won't be
    able to find services since dns service records won't be able to be
    consulted. Even a reboot of your dns server could be a temp loss of
    services.

    --
    Paul Bergson
    MVP - Directory Services
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, 2003, 2000 (Early Achiever), NT4
    Microsoft's Thrive IT Pro of the Month - June 2009

    http://www.pbbergs.com

    Please no e-mails, any questions should be posted in the NewsGroup This
    posting is provided "AS IS" with no warranties, and confers no rights.
     
    Paul Bergson [MVP-DS], Aug 4, 2009
    #4
  5. Hello Peter,

    Yes, just install DNS server role and wait, cancel all questions to configure
    DNS server/zones popping up.

    If everything is replicated it shouldn't have any influence on Exchange.
    But why will you remove DNS from it, better have 2 DNS servers in the domain
    for failover and redundancy?

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Aug 4, 2009
    #5
  6. Peter Hatzis

    Peter Hatzis Guest

    Hello everyone, thanks for the info. The zone is AD intergrated already. The
    reason i want to transfer the zone is because the DNS server (also exchange
    server) will be reinstalled (new hdd's) and i don't want to backup/restore
    the system. after running for 6 years it carries many unwanted things that i
    don't want to restore. So i thought to move the zone to another server and
    after re-installing the server, move it back to the original server.

    On the other hand, i don't know the impact of doing this:
    Don't move the zone at all, uninstall DNS service without deleting the zone,
    make the appropriate tasks to reinstall OS and configure DNS in the new OS
    from scratch.
    Will this also work?
     
    Peter Hatzis, Aug 4, 2009
    #6
  7. Hello Peter,

    If you will install the server complete from scratch, how do you handle Exchange?
    Do you move it to another server before, btw. DCs are not recommended for
    Exchange install?

    You also have to make the second DC Global catalog server and transfer the
    5 FSMO roles before demoting/removing the DC.

    Also you have to demote the DC to remove it from the domain correct, which
    require also to uninstalll exchange before. Of course you can remove the
    DC the hard way and clenaup AD after that with ntdsutil.

    So if you give some more infos about the way you like to do itwe can give
    you additional infos.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Aug 4, 2009
    #7
  8. Peter Hatzis

    Peter Hatzis Guest

    Hello. The task is as follow:
    Transfer FSMO roles from Exchange to another server (also make it GC)
    Complete system backup
    demote exchange server without uninstalling exchange. exchange can't be
    install when it contains mailboxes. won't move it to another server. the
    server can be demoted while exchange is installed

    install new server + updates.
    promote server to dc.
    Exchange setup /disasterrecovery + updates.
    restore and mount databases.

    i don;t know how to handle dns service. move it to another server, or
    configure dns again when new server is ready?

    Regards, Peter
     
    Peter Hatzis, Aug 4, 2009
    #8
  9. Hello Peter,

    You can NOT demote a domain controller when exchange is installed. Exchange
    MUST be uninstalled before. So you have to do it the hardware with using
    ntdsutil to remove all DC entries from the database.

    Did you ever before restored Exchange that way for testing and know the correct
    steps to do?

    As said before you should always have at least 2 DNS servers per domain.
    When it is on a DC just install DNS server role and wait as before with the
    other one.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Aug 4, 2009
    #9
  10. Peter Hatzis

    Peter Hatzis Guest

    Well yes, i tested the whole task in test enviroment succesfully. Why can't
    i demote the server? There are several articles about restoring exchange to
    same hardware and keeping tha same computer name and exchange parameters
    (organization etc). The disasterrecover switch isn't for these cases?


    in message
     
    Peter Hatzis, Aug 4, 2009
    #10
  11. Hello Peter,

    If you run dcpromo when exchange is installed you will see the error message.

    For disaster recovery see also here:
    http://technet.microsoft.com/en-us/library/bb125070(EXCHG.65).aspx

    If a server crashes and you have to reinstall from scrathc you have also
    to cleanup AD database before. Otherwise you are not able to add a machine
    with the same computer name.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Aug 4, 2009
    #11
  12. Can't demote an Exchange server. O/S won't allow it.

    --
    Paul Bergson
    MVP - Directory Services
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, 2003, 2000 (Early Achiever), NT4
    Microsoft's Thrive IT Pro of the Month - June 2009

    http://www.pbbergs.com

    Please no e-mails, any questions should be posted in the NewsGroup This
    posting is provided "AS IS" with no warranties, and confers no rights.
     
    Paul Bergson [MVP-DS], Aug 4, 2009
    #12
  13. Hi Paul,

    Peter said they're both DCs, so yep, neat trick! But of course with Peter's
    first post, I didn't know they were both DCs, hence why I gave him both
    options.

    Ace
     
    Ace Fekay [MCT], Aug 4, 2009
    #13
  14. Peter,

    You cannot demote a DC with Exchange on it. There is a Microsoft article
    that also specifically states this (posted below in my blog). You literally
    have to setup another Exchange server and move all mailboxes, then replicate
    all pub and hidden system folders to it, then remove the replicas and then
    uninstall Exchange, then demote the machine.

    If you are going to do a disasterrecovery that way, which I don;t really
    advise, because here is your chance to keep Exchange off a DC, which is
    highly recommended. This is a defacto that engineers familiar with Exchange
    and AD follow. Exchange on a DC kills Exchange performance because a DC
    disables write cache on the controller, which Exchange needs, as well as
    complicates recovery. No, you can enable that feature either on a DC. It
    will automatically revert to disabled status.

    Read the following. I had to do something similar for a customer back in Feb
    with a similar issue.

    ======================================================================================================
    Moving to a new Ex2003 currently on a Win2000 server, installing Win2003 DC
    in an existing 2000 AD and removing Ex2000.
    By Ace Fekay, MCT, MCTS Exchange 2007, MCSE & MCSA 2000/2003, MCSA Messaging
    Feb 10, 2009
    ---

    I just did this for a client 3 months ago without a hitch. Here are the
    steps. Keep in mind, if you want to demote a Win2000 DC to a member server
    that has Ex2000 installed, it cannot be done. Ex2000 must be removed first,
    then the DC can be demoted. Follow the steps to install a new 2003 DC, then
    install Ex2003 either on this or a member server (recommended), move
    everything tothe new Ex2003, then remove Ex2000 off the old DC, then demote
    it.

    1. Run the command in this article to fix the mangled attributes in your
    current domain. This is because Ex2000 creates two incompatible attributes
    that Win2003 cannot use since it was updated in 2003 AD. Follow the steps
    under "Scenario 2: Exchange 2000 Schema Changes Are Installed Before You Run
    the Windows Server 2003 adprep /forestprep Command"

    Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in
    Windows 2000 Forests That Contain Exchange 2000 Servers:
    http://support.microsoft.com/kb/314649

    2. Then promote the W2003 as a DC in the existing domain.

    3. Move the FSMOs and the GC to the new server.Allow replication to take
    place and insure that the new DC has taken on the FSMO roles and it became a
    GC. Check DNS to insure that it's now registerd as a GC.

    4. Install Ex2003 as an additional Exchange server in the existing
    organization. You can install it on the new DC, but rather on a separate
    W2003 member server (highly recommended).

    5. In AD, rt-click, Exchange Tasks, move all mailboxes to the new Ex2003
    server.

    6. Move ALL Public and System (hidden) folders to the new Ex 2003 server.
    Follow these articles and look for the section about "Migration of mailboxes
    and public folders". This is extremely important because the system folders
    are only created at time or the Ex organization creation. If you don't do
    this and remove the first server, it's possible to recreate them, but it's
    extremely difficult.

    822450 - How to Remove the Last Exchange Server 5.5 Computer from an
    Exchange Server 2003 Administrative Group (Look at "Migration of mailboxes
    and public folders"):
    http://support.microsoft.com/default.aspx?kbid=822450&product=exch2003

    822450 - How to Remove the Last Exchange Server 5.5 Computer from an
    Exchange Server 2003 Administrative Group (Look at Step 4 about how to view
    the System

    Folders and how to replicate them and remove the original instances):
    http://support.microsoft.com/kb/822450

    Step-by-Step Migrating Exchange 2000 to Exchange 2003 Using New Hardware:
    http://www.msexchange.org/tutorials/Migrating-Exchange2000-Exchange-2003-Hardware.html

    7. Once you've verified the folders are all moved, mailboxes are working,
    then run the Ex 2000 setup and remove (uninstall) Ex2000 off of the original
    machine.

    8. Double check in ADSI Edit, configuration container, Services, Exchange,
    drill down to the server list, and insure that the original one is gone.


    Additonal links about removing Exchange:

    How to remove Exchange Server 2003 from your computerThis how-to article
    describes the steps to automatically or manually remove Microsoft Exchange
    Server 2003 from your computer. Before you can remove ...
    http://support.microsoft.com/kb/833396

    How to completely remove a Exchange server or the entire Exchange ...Oct 19,
    2004 ... Remove the Exchange 2003 server object from the Exchange 5.5 Admin
    .... How to Remove the First Exchange 2003 Server Computer from the Site ...
    http://www.msexchange.org/tutorials/Remove-Exchange-server-entire-Exchange-organization.html

    Removing The Last Exchange 2003 Server From Exchange 2007 (Part 1)Jun 5,
    2008 ... The steps required in order to remove the last Exchange 2003 server
    from an organization that has been migrated to Exchange 2007.
    http://www.msexchange.org/articles_...exchange-2003-server-exchange-2007-part1.html

    How to remove the first Exchange Server 2003 computer from the ...This
    article describes the steps to remove the first Microsoft Exchange Server
    2003 computer from an administrative group. The first Exchange Server 2003
    ....
    http://support.microsoft.com/kb/822931

    CANNOT REMOVE EXCHANGE 2003 SERVER FROM ACTIVE DIRECTORY:
    http://www.experts-exchange.com/OS/...Windows_2003_Active_Directory/Q_22501384.html
    =======================================

    Ace
     
    Ace Fekay [MCT], Aug 4, 2009
    #14
  15. Peter Hatzis

    Peter Hatzis Guest

    Hello everyone thanks for the info. I am totally confused though!!! As i
    told you, i demoted the exchange server, reinstalled Windows and exchange
    (/disasterrecovery mode) and mounted the databases. The task was successful,
    and no errors are logged. Clients can connect, owa works.
    What can i say? Since i am not an exchange expert, i will try in test
    environment again, the procedure you recommend (installing second exchange
    server and transferring data).

    Once more, thanks for you help
     
    Peter Hatzis, Aug 5, 2009
    #15

  16. I'm really surprised that in your first test environment with Exchange on a
    DC, it actually let you demote it. It should have come up with an error when
    you tried it.

    Ace
     
    Ace Fekay [MCT], Aug 5, 2009
    #16
  17. Hello Peter,

    Do we maybe misunderstand you, you can not demote exchange, you demote a
    domain controller, mabe it wasn't a DC?

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Aug 5, 2009
    #17
  18. Peter Hatzis

    Peter Hatzis Guest

    Hello.
    The server originally is DC (not member) + FSMO + global catalog and has
    exchange 2003 installed (with all updates)
    FSMO is moved to another DC
    GC is removed

    So, i have now a dc with exchange 2003 which contains all user maiboxes

    I demoted the server without any errors. reinstalled windows. before
    promoting again to dc, i "reset account" in active directory using the other
    server. the server was promoted with same computer name without any errors.
    No errors in Directory Service and File Replication Service logs.

    I will run the same scenario again and let you know.
    Regards, Peter
     
    Peter Hatzis, Aug 5, 2009
    #18
  19. Hmm. When I tried it long ago, it wouldn't let me...

    But keep in mind, if you were to keep the now demoted DC with Exchange on
    it, there will probably be errors because when Exchange is on a DC, it locks
    itself to this DC for DS info.

    Let me know how you make out.

    Ace
     
    Ace Fekay [MCT], Aug 5, 2009
    #19
  20. Peter Hatzis

    Peter Hatzis Guest

    Hello. After testing for second time, the results are:

    as told, i have a dc with exchange 2003 installed and all user mailboxes.
    running dcpromo and restart, results to a member server which ofcourse can
    still run exchange server normally. All services start and clients can
    connect.

    Right click to my computer - Properties - Computer Name - Change.
    Change from domain company.gr to workgroup company. Settings are accepted
    and a reboot is required for the changes to take effect. After rebooting i
    have a win2003 stand alone server. Exchange services don't start.

    Reinstall windows + updates with same computer name ip address etc. "Reset
    account" in active directory. Promote server to dc. install exchange
    /disasterrecovery. restore and mount databases.
    Services are started and clients can connect (outlook + OWA)

    I don't know. perhaps someone can test it too and let me know.
    Regards, Peter
     
    Peter Hatzis, Aug 6, 2009
    #20
    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.