[Solve]The fully qualified domain name for node could not be found.
On my last blog, I had a talk about DAG (Database Availability Group) on Exchange 2016. Fortunately, I had smooth configuration but luck doesn’t go every day like that. Here is one of the issue you might face during the configuration of DAG and also I have posted resolution on it.
Issue:
A server-side database availability group administrative operation failed with a transient error. Please try the operation again. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: “CreateCluster() failed with 0x5. Error: Access is denied” [Server: WS2K12R2EXG01.pdhewaju.com.np]
error
The fully qualified domain name for node ‘DAG’ could not be found.
An Active Manager operation failed with a transient error. Please retry the operation. Error: The fully qualified domain name for node ‘<NameofYourDAG>’ could not be found.
Resolution:
During the DAG creation, it will automatically create an DAG computer. If the error comes as of above, go to the properties of your DAG Computerà Attribute Editor and check if you do have FQDN value on ‘dNSHostName’. If not add it as on the snapshot.
Thank you
Bulk User Import on Active Directory
Disabling Basic Authentication on Exchange Online
Restrict Group Creation in Office 365
About Author
pdhewjau
Prashant is a Principal Cybersecurity Specialist at Thakral One Nepal. His prior position as a Modern Work Security Specialist at Microsoft saw him providing invaluable guidance to major clients in Bangladesh, Brunei, Cambodia, and Myanmar, assisting them with their foundational security needs. Awarded the esteemed Microsoft Most Valuable Professional (MVP) accolade in 2017, Prashant is recognized globally among Microsoft peers. Since 2010, he has imparted his expertise as a Microsoft Certified Trainer (MCT), conducting specialized training across Nepal.
Add a Comment
This site uses Akismet to reduce spam. Learn how your comment data is processed.
The fully qualified domain name for node ‘Server1’ could not be found. This Server1 is old exchange server which is now does not exist. Its Exhcange 2016 CU9.