Will the various KMS client versions (Windows, Office) handle CNAMEs as expected (i.e. resolve the referenced destination RRs) when resolving the
_vlmcs._tcp.<localdomain> KMS machine name from DNS?
The rationale here: we have an environment with a sh!tload of subdomains, our Windows clients and servers (not necessarily domain-joined) are scattered among all of them. Our DNS management for these domains is rather inflexible (we can handle changes once in a while, but it is onerous) whereas we have some domains delegated to AD DNS servers where changes are easily implemented. We would have
_vlmcs._tcp.<localdomain>. IN CNAME _vlmcs._tcp.addns.domain. RRs created all over to ease up KMS server addidion and replacement.
I am able to test the basic functionality (Win7 + Server 2008 R2 / Server 2012 R2 clients, Office 2013) without major effort. Yet, I do not have a sufficiently large sample size of different OS versions, Office installations, service packs and possibly KMS-client-related hotfixes to tell if it would work in all common configurations.