# Data Object - VsanFileServiceDomainConfig(vim.vsan.FileServiceDomainConfig)

Property of
  VsanFileServiceConfig, VsanFileServiceDomain
Parameter to
  VsanClusterCreateFsDomain, VsanClusterReconfigureFsDomain, VsanPerformFileServiceEnablePreflightCheck
Extends
  DynamicData
See also
  VsanDirectoryServerConfig, VsanFileServiceIpConfig
Since
  vSAN API 7.0

## Data Object Description

A vSAN File Service Domain is unique namespace. Network and security configuration can be uniquely set for this namespace. One or more file shares be managed with this namespace. A file service domain may be integrated with a Directory Service like Microsoft Active Directory, although this integration is not mandatory. Note: vSAN File Service doesn't support mix mode for IPv4 + IPv6 network, so it will report error if both IPv4 and IPv6 configurations are detected.

Properties

Name | Type | Description
--- | --- | ---
directoryServerConfig* | VsanDirectoryServerConfig | The directory server integrated with for the domain. If Directory server configuration is provided NFS shares can be configured with KRB5 authentication, otherwise only AUTH_SYS(sys or unmanaged client) configs are allowed. Since vSAN API vSAN 7.0U1
dnsServerAddresses* | xsd:string[] | The IP address of DNS server address, which is used to resolve the hostnames within the DNS domain. Providing this parameter is a must for file service domain creation operation.
dnsSuffixes* | xsd:string[] | The list of DNS suffixes which can be resolved by the DNS servers. An exhaustive list of all DNS domains and subdomains from where clients can access the file shares must be provided. Providing this parameter is a must for file service domain creation operation.
fileServerIpConfig* | VsanFileServiceIpConfig[] | Define a pool of IP addresses that will be used by vSAN File Service to provide file access from multiple file server. Each file server will be bound to one of the IP configurations in the IP pool and serve the NFS requests. A minimum of one such address is needed, more may be required based on load and number of shares. To evenly spread the workload, it is recommended to have equal (or greater) number of IP addresses than the number of hosts in the cluster. All the IP address will be required to be on the same subnet. One primary IP must be specified for the NFS referral server. All the file shares on vSAN file service can be listed and accessed with this primary IP. When a referral is encountered, the NFS client will automatically receive the actual managing file server location from referral server with the primary IP. This field is required for domain creation.
name* | xsd:string | The vSAN File Service domain name should be unique within a vSAN cluster, Any valid unique identifier can be used as name. No white spaces and special characters(except _ - .) with length of the domain name limited to 80 char. It is not necessary to associate this domain with any Directory Service (AD domain). This field is required for domain creation.
version* | xsd:string | The domain config version. It is recommended to leave this field unset to let the domain configuration negotiated between the vCenter and ESXi. Since vSAN API vSAN 7.0U1
Properties inherited from DynamicData
None

*Need not be set
Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="VsanFileServiceDomainConfig"> <complexContent> <extension base="vsan:DynamicData"> <sequence> <element name="name" type="xsd:string" minOccurs="0"/> <element name="dnsServerAddresses" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <element name="dnsSuffixes" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <element name="fileServerIpConfig" type="vsan:VsanFileServiceIpConfig" minOccurs="0" maxOccurs="unbounded"/> <element name="directoryServerConfig" type="vsan:VsanDirectoryServerConfig" minOccurs="0"/> <element name="version" type="xsd:string" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType>