It's possible to manipulate the list of Domain Controllers through the ODM AD Dirsync menu, Environments, select affected environment, Settings, Domain Controllers. Simply add a working domain controller there and remove the problematic one.
Please note, that for SIDHistory purposes, DC with PDC Emulator role must be present in the list. Preferably with the highest priority. This applies to the source environment only.
Before adding the new DC to the list, please make sure to install a Quest password plugin on it, with the same passphrase, if Modern password sync is in use. And make sure that "modern" checkbox is checked after the addition.
Lastly, please check on dirsync agent machines, registry, under HKEY_LOCAL_MACHINE\SOFTWARE\Quest\On Demand Migration For Active Directory\ODMAD_DS\Agent#. There's a value of "entry point" DC/GC machine is this is not a problematic DC. If it is, simply populate FQDN of the working DC/GC machine and restart the dirsync agent service (name starts with On Demand...).
Note: please make sure to stop any running workflows gracefully before restarting the agent service.
