Technical Tip: Windows DNS server settings for FortiClient EMS multitenancy
Description
This article described how to configure A-Record on Windows DNS server when a FortiClient EMS multitenancy is enabled.
Scope
For FortiClient EMS 6.4.2.
Solution
When multitenancy is enabled, Fabric connectors must use a FQDN to connect to EMS, where the FQDN hostname matches a site name in EMS (including 'default').
The following are the examples of FQDNs to provide when configuring the connector to connect to the default site and to a site respectively.
The example is default.ems.yourcompany.com, site1.ems.yourcompany.com, site2.ems.yourcompany.com, site3.ems.yourcompany.com and so on.
It is necessary to create the A-record for each site for the corresponding third level domain or FQDN.
Sample as follows for Windows DNS server.

This article described how to configure A-Record on Windows DNS server when a FortiClient EMS multitenancy is enabled.
Scope
For FortiClient EMS 6.4.2.
Solution
When multitenancy is enabled, Fabric connectors must use a FQDN to connect to EMS, where the FQDN hostname matches a site name in EMS (including 'default').
The following are the examples of FQDNs to provide when configuring the connector to connect to the default site and to a site respectively.
The example is default.ems.yourcompany.com, site1.ems.yourcompany.com, site2.ems.yourcompany.com, site3.ems.yourcompany.com and so on.
It is necessary to create the A-record for each site for the corresponding third level domain or FQDN.
Sample as follows for Windows DNS server.

With that configuration, it is also possible to use the created A-record to management access to each site by the respective site administrator via browser to perform a configuration.
Example.
https://default.ems.yourcompany.com
https://site1.ems.yourcompany.com
https://site2.ems.yourcompany.com
https://site3.ems.yourcompany.com
https://site1.ems.yourcompany.com
https://site2.ems.yourcompany.com
https://site3.ems.yourcompany.com