Home > Tintri VMstore™ > Knowledge Base > VMstore, naming and DNS

VMstore, naming and DNS

Table of contents

Applies To


Product(s): All

Product Version(s): 3.1.1 and later


Hyper-V support and other features bring with them a dependency on fully functioning DNS and correct DNS records. This is primarily due to the reliance by Hyper-V on Active Directory and Kerberos authentication. Incorrect naming or DNS records can cause some functionality to appear to fail in unintuitive ways. This article details the minimal work set of names around VMstore for Hyper-V support.

  1. Management hostname (eg, vmstore01.vmlevel.com)
    • Assigned at install time as the hostname
    • Used as the name of the Active Directory computer account when joining the domain (eg, vmstore01)
    • Set as user principal name on Active Directory computer account (eg, HOST/vmstore01)
    • Must be resolvable in DNS to the management IP address of the VMstore only (eg, vmstore01.vmlevel.com)
  2. SMB hostname (eg, vmstore01-data.vmlevel.com)
    • Assigned in the VMstore UI when configuring Hyper-V support
    • Set on Active Directory computer account as the cifs/ service principal name (eg, cifs/vmstore01-data.vmlevel.com)
    • Must be resolvable in DNS to the data IP of the VMstore only. Multiple data IPs may be used in some cases, but can cause difficult-to-diagnose issues if not done correctly (eg, vmstore01-data.vmlevel.com).

Another way to look at the relationship between all of these names is:

  • One Active Directory computer account based on management hostname, which contains:
    • A user principal name based on the management name
    • A service principal name based on the SMB hostname
  • A DNS record for the management hostname that resolves to the management IP
  • A DNS record for the data path (SMB) hostname that resolves to the data IP

There is no requirement by VMstore for reverse DNS lookups to succeed.


You must to post a comment.
Last modified
03:24, 26 May 2017



This page has no classifications.