Hi Manon David,
The core of this issue lies in the client's inability to locate the KMS host via DNS. You must verify that the Service Location record, specifically _vlmcs._tcp in your Forward Lookup Zone, exists and points to the correct KMS host server. This record allows the Windows client to dynamically discover the activation service without manual intervention. If this record is missing or misconfigured, the client will fail the handshake, resulting in the error you are seeing.
Once you have ensured the DNS infrastructure is correct, you can force the client to re-establish the connection. Open an elevated command prompt on a target PC and run slmgr /ckms to clear any existing, potentially incorrect KMS host information cached on the local system. Follow this by running slmgr /skms <KMS_FQDN>:1688 to explicitly point the client to your server, then execute slmgr /ato to trigger the activation request. This process effectively resets the discovery mechanism. If the failure persists, verify that your network environment is not blocking TCP port 1688, as the activation traffic must pass freely between the client and the KMS host.
Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN