AD server with all FSMO roles installed got crashed and no longer accessible

Suravind R 21 Reputation points
2022-10-12T10:28:38.777+00:00

Hi,

I have one AD/DNS server with all FSMO roles installed. Now that server is not switching on. I am not able to access additional domain controller as it says "Naming information cannot be located because: specified domain either doesnot exist or could not be contacted".

Can any one help me to troublehoot this, as the primary DC will no longer available.

Thanks
Suravind

Windows for business | Windows Client for IT Pros | Directory services | Active Directory
Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

Accepted answer
  1. JimmySalian-2011 42,611 Reputation points
    2022-10-12T10:38:20.91+00:00

    Hi @Suravind R ,

    In this case you will have to seize the FSMO roles from the failed DC, follow the steps from this article transfer-fsmo-roles-from-failed-domain-controller
    transfer-or-seize-fsmo-roles-in-ad-ds

    Hope this helps.

    ==
    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Limitless Technology 44,781 Reputation points
    2022-10-13T09:13:09.803+00:00

    Hello there,

    You can seize the FSMO role, but never & ever connect the DC with whom you have seized the FSMO role, even though its works fine post-seizing the FSMO role. The right method is once the role has been seized from the DC perform the metadata cleanup of the failed DC & allowed it to replicate the changes & freshly install the OS on crashed DC not mandatory but a good way to go.

    The error "The Specified Domain Either Does Not Exist or Could Not Be Contacted" commonly occurs due to invalid DNS settings on the workstation's side because Active directory requires you to use domain DNS to work properly.

    To resolve the "Specified Domain Does Not Exist or Could Not Be Contacted" error, you have to set the Preferred DNS IP to point to Primary Domain Controller's IP address, on each client workstation that you want to join in the domain.

    The below thread discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue.

    https://social.technet.microsoft.com/Forums/en-US/091a1ea6-88c3-4a43-96eb-3969cd90c20a/the-specified-domain-either-does-not-exist-or-could-not-be-contacted?forum=winserver8gen

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/4fcce8da-5b34-416d-8aed-4fe0074e2058/what-if-a-dc-fails-that-had-all-fsmo-roles?forum=winserverDS

    --------------------------------------------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept it as an answer–

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.