ODMAD Dirsync error: "Write: No available DCs for domain, cannot process LDAP request for object:" (4324961)

ODMAD Dirsync error: "Write: No available DCs for domain, cannot process LDAP request for object:"

Attempting to write user upn@domain.com and receiving the error "Write: No available DCs for domain, cannot process LDAP request for object:". 

This exception "No available DCs for domain, cannot process LDAP request for object" will occur when DirSync cannot locate the object based on the object DN in the specified Global Catalog Server. DirSync will search the object based on the DN via the specified DCs in the DC list.

or

The target contact object was deleted.

The issue can also be caused by template, attempting to use copy (Basic) source distinguishedName to the target in Mappings.

Verify this users DN is correct. Additionally, reconnecting the tenant may help.  This can be done from the 'Settings' gear icon - 'Environments' tab

Highlight the object and click the 'Reconnect' action hotspot.

Confirm in workflow logs if a target contact object was created previously by ODMAD, and if there was a previous attempt at migrating this account had been deleted from the target Active Directory.
If yes, restore the target contact, then the preparation, sync and cutover for the account should work correctly.

Check workflow, Stage and what template it's using, then go to hamburger menu, templates. Find this template, select it and click on Settings.
Click on Mapping and search for distinguishedName. Make sure this it's not set to Basic (simple copy) of the source DN. Default setting for DN mapping is Advanced and GetDN(cn) in the Value section

Trying to use this exact DN in the target domain (e.g., DC=target,DC=domain,DC=com), the LDAP Add operation will attempt to locate that DN in the target domain's directory. But here's the catch: - The DN still references the source domain's structure, which doesn't exist in the target domain. - The LDAP client tries to resolve this DN by contacting a Domain Controller (DC) that can handle it. - Since the DN points to a domain that doesn't exist or isn't reachable from the target environment, the system throws a misleading error: "DC cannot be found or not responding."