The DNSUpdate.exe process updates the primary A name record for the server, not the C name as outlined in this KB article.
You could theoretically execute your own dnscmd.exe process to update a specified C name record instead of using the DNSUpdate.exe.
Thanks for the reply. That is a possibility.
One thought I had was there does seem to be an option on the WAN set up (to avoid the split brain scenario) to set up a secondary IP on the main public interface on the 2 machines. I'm wondering if it would be better to tie the machine names to the A/PTR records for those addresses instead and then use the other hostname (the one that the FoE updates the IP for on failover) as our primary Orion address as it were. Don't know if that is possible? May have to do a little experimenting.
