DNS Errors prevent replication

  • Thread starter Thread starter Aaron
  • Start date Start date
A

Aaron

I have two W2K servers which are currently unable to replicate AD. One
of the servers (Server1) is running Exchange 5.5 and also is has a
different DNS domain name than the rest of the domain. For example, all
of the machines in our BIGCOMPANY domain have the DNS suffix of
BIGCOMPANY.COM except this one server. The other server (Server2)
participating in AD has the appropriate DNS suffix.

What I was thinking of doing is demoting the machine with the
questionable domain membership, making it a member server, uninstalling
DNS, promote back to Domain Controller and reinstalling DNS. DNS is
running on Server2, so I probably do not have to reinstall DNS on
Server2, but would like to for redundancy.

Basically my goal is to just get DNS working correctly so replication can
occur.

I have seen the MS article regarding demoting, but am interested in
hearing any additional comments, especially regarding the Exchange 5.5
installation and the viability of success.

Thanks,
Aaron
 
Hi Aaron-

If you are demoting a DC since it is not replicating with another DC or DCs
you need to add an additional step(s).

First, the demotion will not succeed (most likely) unless you use the
DCPROMO /FORCEREMOVAL switch. This is available in SP4 of Windows 2000 and
inherently on Windows Server 2003.

Next, you'll need to remove references to the demoted DC from the remaining
DC per the article below. If you have multiple DCs in your domain or forest
you'll want to make sure that the removal replicates to all domain
controllers.

216498 HOW TO: Remove Data in Active Directory After an Unsuccessful Domain
http://kb/article.asp?id=Q216498

Please repost if you have any questions or concerns.
 
Back
Top