Server2012: Adding DAG Member Results in ‘The fully qualified domain name for node ‘EMEA-SWEEX15-01′ could not be found.’

NOTE: This post – drafted, composed, written, and published by me – originally appeared on https://blogs.technet.microsoft.com/johnbai and is potentially (c) Microsoft.

To get around this, add the permissions by following this article for pre-staging the Cluster Name Object for a Database Availability Group. If you still receive the error, modify the ‘dNSHostName’ attribute to reflect the FQDN of your DAG, as referenced below from my lab (suffix removed from screenshot):

5 thoughts on “Server2012: Adding DAG Member Results in ‘The fully qualified domain name for node ‘EMEA-SWEEX15-01′ could not be found.’

  1. Thanks! This fixed the "The fully qualified domain name for node ‘DAG1’ could not be found." error.

  2. The fully qualified domain name for node ‘Server1’ could not be found. This Server1 is old server.

Comments are closed.