Categories: Exchange

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

During move of database to a different Exchange 2013 server an error is displayed:

“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 ‘<Your DAG Name>’ could not be found.”

⚠️ Problem Description

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 ‘<Your DAG Name>’ could not be found.

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

✅ Solution

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 “<Your DAG Name>” in Active Directory if it's enabled. Otherwise you will get an error about it during adding of servers to DAG.

If everything goes well you should see success message that the move operation is complete.

This post was last modified on June 6, 2025 19:06

Przemyslaw Klys

System Architect with over 14 years of experience in the IT field. Skilled, among others, in Active Directory, Microsoft Exchange and Office 365. Profoundly interested in PowerShell. Software geek.

Share
Published by
Przemyslaw Klys

Recent Posts

Supercharging Your Network Diagnostics with Globalping for NET

Ever wondered how to run network diagnostics like Ping, Traceroute, or DNS queries from probes…

7 days ago

Automating Network Diagnostics with Globalping PowerShell Module

Are you tired of manually running network diagnostics like Ping, Traceroute, or DNS queries? The…

1 week ago

Enhanced Dashboards with PSWriteHTML – Introducing InfoCards and Density Options

Discover new features in the PSWriteHTML PowerShell module – including New-HTMLInfoCard, improved layout controls with…

2 weeks ago

Mastering Active Directory Hygiene: Automating SIDHistory Cleanup with CleanupMonster

Security Identifier (SID) History is a useful mechanism in Active Directory (AD) migrations. It allows…

2 weeks ago

Upgrade Azure Active Directory Connect fails with unexpected error

Today, I made the decision to upgrade my test environment and update the version of…

2 weeks ago

Mastering Active Directory Hygiene: Automating Stale Computer Cleanup with CleanupMonster

Have you ever looked at your Active Directory and wondered, "Why do I still have…

2 weeks ago