question

Hi @Szunomar,
Try to verify the KMS key in host computer, please follow these steps:

From an elevated command prompt on the KMS host computer, run the following command:

 cscript slmgr.vbs /dlv all

To view information only for Office 2019, specify the Activation ID after the /dlv parameter. For example:

 cscript slmgr.vbs /dlv 70512334-47B4-44DB-A233-BE5EA33B914C

Then post the output text here, you can check if the License Status: Licensed.

Then I suggest you refer to this article about "configure DNS for activating volume licensed versions of Office by using KMS":
https://docs.microsoft.com/en-us/deployoffice/vlactivation/configure-dns-to-activate-office-by-using-kms

Make sure the DNS is configured correct.

Just checking in to see if the information was helpful. Please let us know if you would like further assistance.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Hi there,

Verify that the KMS activation threshold is met. On the KMS host computer, run Slmgr.vbs and use the /dli command-line option to determine the host’s current count.

The below thread discusses the same issue and you can try out some troubleshooting steps

from this and see if that helps you to sort the Issue.
DNS auto-discover: KMS name not available https://social.technet.microsoft.com/Forums/exchange/en-US/c5b1d243-8051-427d-b190-4e3da9d5847e/dns-autodiscover-kms-name-not-available?forum=officeitpro

I also suggest you refer to this article about "configure DNS for activating volume licensed versions of Office by using KMS" to check if you have configured the KMS properly.

https://docs.microsoft.com/en-us/deployoffice/vlactivation/configure-dns-to-activate-office-by-using-kms

---

--If the reply is helpful, please Upvote and Accept it as an answer--

Ok Guys, we have the trick in the process.

After installing the Windows if you use the "slmgr.vbs /skms:<FQDN or IP>" command to set a static KMS server (here it was directly coded in our Windows installer), the Office 2019 won't use anymore the MKS-Autodiscovery DNS records. They just try to use the KMs from Windows.
In our case, this old server had only licences for Win10, not for OPP2019 (even that is why we want to use the new one, offered from DNS)

So the solution is: man have to use the "slmgr.vbs /ckms" command to delete the KMS server defined to Windows. "ospp.vbs /remhost" command will not clear it and even "ospp.vbs /skms:<FQDN>" will not overwrite it. That is two different record in registry, but the Office uses the Windows-Record if it exists and an Office-Record doesn't exists.

After cleared the record, the Offices started to be Licenced. Well done.

Unfortunately the weight or priority isn't used by clients from _vlmcs._tcp SRV records so i haven't found any way to force the use of DNS instead of registry records.