Cannot add new DC with old dead DC IP

Question

Our secondary DC crashed, and i had to create a new secondary dc as many users have it configured as their preferred DNS server.
The promotion of the new secondary keeps failing whenever I use the same IP as the dead DC.
PS: I have removed all references to the old dc on the domain before recreation.
I tried changing the IP after using a new IP to create, but it stops replicating to the PDC once that's done.
What do I do? manually changing the DNS for all users will be very tasking.

Answer 1

Sounds like some cleanup may be necessary.
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt
ipconfig /all > C:\dc3.txt
ipconfig /all > C:\problemmember.txt

then put unzipped text files up on [OneDrive][1] and share a link.

Answer 3

Is it possible the IP was taken by another device? Can you ping the IP? Also try checking your switch logs to see if the IP is reported anywhere.

Answer 4

I took down all the secondary DC and brought up a new secondary DC, on bringing it up replication with the PDC was successful but after 24hrs replication is failing currently. The new Secondary DC has been created with an entirely new IP.

Answer 5

You can try a non authoritative sync
https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

--please don't forget to upvote and Accept as answer if the reply is helpful--