Pointing the config to another DC should make the error go away.
However if you are attempting to use SID History, auditing should be enabled for that DC. In other words, when running the ODM AD Dirsync Agent setup wizard, the tool can be directed to one DC for sync and another DC for SID History.
That should enable for you to get this all to work. Otherwise, the SID sync will fail unless you enable auditing on the new server in scope.
