blog

Exchange 2013 SP1 – The fully qualified domain name for node ‘DAG-EX2013’ could not be found.

During a move of a mailbox database to a different Exchange 2013 server, this error appeared:

“The fully qualified domain name for node ‘DAG-EX2013‘ 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 ‘’ could not be found.”

What the error looks like

An error message is displayed either in Exchange Control Panel or Exchange Management Shell:

The fully qualified domain name for node ‘DAG-EX2013' 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 ‘ ’ could not be found.

While the exact reason why this happens is unknown there's a fix to address this issue.

What fixed it

To fix this:

  1. Go to Active Directory Users and Computers
  2. In ADUC be sure to turn on View > Advanced Features
  3. Search for a computer object that represents your DAG. ie So if you name your DAG “Exchange 2013 DAG” you will have a computer object call this in AD.
  4. Right Click > Properties
  5. Under General tab, if you DNS name is empty, goto Attribute Editor tab
  6. edit Attribute “dNSHostName” and add your FQDN of the DAG, so like “DAG-EX2013.YOUR.LOCAL.DOMAIN”
  7. Hit OK and wait for AD replication. Then try to re-add the server to the DAG

You may also need to disable the object “” in Active Directory if it's enabled. Otherwise you will get an error about it during adding of servers to DAG.

Why this matters

Exchange DAG operations rely heavily on the related computer object state in Active Directory. If the DAG object is missing the expected DNS identity information, the failure message can look like a transient Exchange problem when the real issue is directory metadata.

So if the error mentions that the fully qualified domain name for the node cannot be found, it is worth checking the DAG object itself instead of focusing only on the mailbox server services.

If everything goes well, you should see the move operation complete successfully.

Saving Completed Sucessfully