Skip to main content

Creating DNS Records for Accessing the KMS Server

This article applies to: Software Licensing


This page is intended for technical support providers and network administrators. If you're not one of those, you should talk to your TSP or net admin before proceeding. The concept behind the procedure on this page is explained on our main KMS page.

This page describes how to register the KMS servers in your DNS domain for autodiscovery.

You'll need to know the Connection-specific DNS Suffix for your domain. Here's how to find that information.

  1. From a Windows computer in your DNS domain, click the Start orb. In the Search box, type
    cmd
    and press Enter.
  2. In the command prompt window, type
    ipconfig /all
    and press Enter.
  3. Take note of the entry following Connection-specific DNS Suffix.
    This is the DNS domain that you will need to specify later in this process.

Next follow the steps below that best describes your domain's setup:

Method 1-A: Using CIT's DNS Servers

Domains that use CIT's DNS servers have all been registered for KMS autodiscovery. No action should be needed.

Method 1-B: Using Local DNS Servers

These instructions assume you are familiar with the DNS server software your department uses.

You will create two records: one for the primary KMS server and another for the secondary (failover) KMS server.

Below you'll find the steps for Windows and for *NIX systems.

Windows Server 2000-2008

  1. Open the DNS Microsoft Management Console (MMC).
  2. Expand the DNS Zone to the Connection-specifc DNS Suffix you noted earlier.
  3. Right-click on the _tcp folder and select Other New Records.
  4. Select Service Location (SRV) as the new record type.
  5. Fill in the following information for the new record:
  • Service: _VLMCS
    (Note: This is not in the drop-down list, so you'll need to type it in. Be sure to include the underscore at the beginning.)
  • Protocol: _tcp
    (Note: Select this from the drop-down list.)
  • Port: 1688
  • Priority: 10
  • Host offering the service: kms01.cit.cornell.edu.
    (Note: Be sure to include the trailing dot.)
  1. Follow the steps above to create a second new SRV record with the following information (the Priority and Host fields are different):
  • Service: _VLMCS
    (Note: This is not in the drop-down list, so you'll need to type it in. Be sure to include the underscore at the beginning.)
  • Protocol: _tcp
    (Note: Select this from the drop-down list.)
  • Port: 1688
  • Priority: 20
  • Host offering the service: kms02.cit.cornell.edu.
    (Note: Be sure to include the trailing dot.)

And you're done.

Bind 8.2 or higher (Linux, Unix, Solaris)

On the DNS server, open the Bind zone file.

Add these two lines to the file, substituting the Connection-specific DNS Suffix you noted above. In our example, we use sheep-shearing.cornell.edu for our DNS suffix; replace that text with yours DNS suffix. Be sure to include the two underscore characters in each line (four in total) and the trailing dots after the DNS suffix and the host names in both lines.

_vlmcs._tcp.sheep-shearing.cornell.edu. 3600 IN SRV 10 0 1688 kms01.cit.cornell.edu.

_vlmcs._tcp.sheep-shearing.cornell.edu. 3600 IN SRV 20 0 1688 kms02.cit.cornell.edu.

Save the file. And you're done.

If you are not able to get KMS working in your domain, please contact us.

About this Article

Last updated: 

Wednesday, December 14, 2016 - 1:06pm

Was this page helpful?

Your feedback helps improve the site.

Comments?