Domain Mess - Problem promoting second server to DC


Our windows 2003 server domain controller (DC1) for NAME.Local was the only
server on our network (running AD / DNS/ DHCP). However, the disk array
began to fail causing serious disk damage and killing 1 disk of 3, with #2
having serious problems. (I think using identical disks from the same
manufacturer needs a rethink, but that's a different story).

I was able to bring up a second domain controller on an old PC (DC2) to
preserve the domain and I transfered the roles that I could throught the
Users/Computers snap-in, but DC1 died before I was able to gracefully demote
it or run ntdsutils for a more comprehensive switchover. Instead, I was
forced to simply delete its object out of the AD that was now running on
DC2.

I have been able to rebuild the DC1 machine and join it as a member server,
but I am getting DNS errors trying to run DCPROMO to turn it back into a
domain controller. I want it to have the same name it always had (DC1) even
though it is now a rebuilt machine.

I installed DNS on DC2, and configured DC2 to use itself for DNS. I
configured the newly rebuilt member machine (the DC1 - wannabe) to use DC2
for DNS, but I am still getting problems with dcpromo on DC1.

HELP! I suspect DNS is somehow not initialized correctly because it was
added to DC2 after the original DC1 died, but I'm not sure how to
methodically fix it. This should not be rocket science....

1) What do I need to do to my temporary domain controller (DC2) to ensure it
has correct DNS?
2) what do I need to do to my rebuilt DC1 machine so that I can repromote
it?

Kate



.

Relevant Pages

  • Re: Jorge --- Re: root forest AD DC crashed
    ... Also install DNS, WINS and DHCP ... Give DC1 it own IP address ... As preferred DNS for DC1 enter the IP of DC1 ... As alternate DNS for DC1 enter the IP of DC2 ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain Mess - Problem promoting second server to DC
    ... So doing this, should I remove my newly rebuilt machine from the domain, do ... It has the same name it had before it died as a domain controller ... >> the AD that was now running on DC2. ... >> I installed DNS on DC2, and configured DC2 to use itself for DNS. ...
    (microsoft.public.windows.server.dns)
  • Re: root forest AD DC crashed
    ... For location A install a fresh W2K3 server with SP1. ... Give DC1 it own IP address ... As preferred DNS for DC1 enter the IP of DC1 ... As alternate DNS for DC1 enter the IP of DC2 ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain controller name -rename issue
    ... Because you did not know what your predecessor have done with the DC1 renaming, i would make sure that the correct existing DC2 have all 5 FSMO roles and is GC server and DNS with AD integrated zones only for the correct old named "domain" domain. ... AD users and computers and AD sites and services is cleaned up you can now promote the old DC1 again to domain controller. ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS SERVICE
    ... Open the dns Management Console on the new dc2 and check to see if the ... domain controller it should offload the five fsmo roles to other domain ... Open AD Users and Computers on ...
    (microsoft.public.windows.server.general)