UCLA's Campus-wide KMS Instructions for DNS Administrators

UCLA System Administrators can configure their machines to locate UCLA's campus-wide KMS service using either of the following two methods. The machines to be activated are required to use a UCLA IP address.

**Note*** if you are not a System Administrator, please visit our Microsoft KMS activation page for non-System Administrators.


Client computer uses the Domain Name System (DNS) service SRV resource records (default) to automatically locate a local KMS host. System Administrators who wish to activate their machines through auto discovery will need to add SRV records to their department's DNS. The KMS system uses SRV resource records to store and communicate KMS location and configuration information through DNS. You can manually create the necessary SRV record for a KMS host. It should contain the following information:

  • Name =_vlmcs._TCP
  • Type = SRV
  • Priority = 0
  • Weight = 0
  • Port = 1688
  • Hostname = FQDN or A-Name of the KMS host

Primary and back-up KMS servers have been set up. It is recommended that you add SRV records for both of them.

  • kms1.softwarecentral.ucla.edu
  • kms2.softwarecentral.ucla.edu

In a sample BIND 9.x zone file, a proper KMS SRV RR looks like this:

  • _VLMCS._TCP IN SRV 0 0 1688 kms1.softwarecentral.ucla.edu
  • _VLMCS._TCP IN SRV 0 0 1688 kms2.softwarecentral.ucla.edu

NOTE: Priority and Weight are not used by the KMS service and are ignored by the KMS client. However, they do need to be included in the zone file.

Here are Detailed instructions on how to configure the necessary SRV entries in Microsoft Windows DNS server for automatic KMS discovery.


A system administrator specifies the KMS host and communication port in the registry. Refer to the Microsoft Volume Activation 2.0 Technical Guide for more information.