NEW SCCM publishing the "DNSHOSTNAME" and "SERVERREMOTENAME" of a secondary site server for Primary Site Server

[johnhammond16]

In a nutshell, we applied the 2107 Hotfix rollup (KB14244456) at the end of September and all seemed to be fine for the next week or so. What we've noticed is that every client we have is now pointing to a secondary site server. When we started digging into it, what we found was that SCCM is publishing itself to the System Management Container with the attribute dNSHostName of one of our secondary site servers. Further digging found that in SysResList, the same thing had happened. The "ServerName" column was correct but the "ServerRemoteName" column had the wrong value. I also found the same value Remote Server Name in the registry on the primary. I've tried updating the registry and republishing as well as editing the value in the System Management container but SCCM republishes the same data overwriting the udpate. We opened a ticket with Microsoft but so far, its been 5 days of getting nowhere and I'm hoping someone else may have seen this and can provide some guidance. We're really stuck here as our network is such that our clients can only reach the primary and 2 secondaries which means most can't reach the secondary they're al currently pointed at anyway.