kms client not activates from lower priority KMS

Testing product activation from low priority KMS.

the situation:

1.

KMS1 is in Domain1 and  provides activation for Office 2013

KMS2 is in Domain2 and  provides activation for Office 2016

KMS2 name entered to DNS of Domain1 with priority 10 (after KMS1 with priority 0)

2.

KMS client with uninstalled Office2013 in Domain1(was activated) and installed Office2016 not activates from the KMS2 that is set and works for Domain2 KMS clients.

Verification steps:

a. KMS client with Office 2016 in Domain1 telnets 1688 of KMS2 (no connectivity issue)

b. nslookup -type=srv _vlmcs._tcp.domain1-FQDN on KMS client in question

correctly outputs KMS1 and KMS2 with set up priorities

The problem:

Office 2016 on KMS client in Domain1 not activates from KMS2 that provides O2016 activation.

Here I come to not approved conclusion (just don't know) that low priorities comes into account when superior is down.

Is it by design or I am missing something in configuration? Can somebody confirm?

From the other hand the message (if it is trusted) in the above status is clear:

DNS auto-discovery: KMS name not available

Then why :

nslookup -type=srv _vlmcs._tcp.domain1-FQDNon KMS client in question

shows correct names and priorities

I will try to shutdown Higher priority KMS for testing this behavior.

Thanks.

--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis