Skip to main content

July 16, 2026 Archived

Create DNS Records and IP Addresses for the Omnissa Access Virtual Appliance

A DNS entry and a static IP address must be available for the Omnissa Access virtual appliance. Because each company administers their IP addresses and DNS records differently, before you begin your installation, request the DNS record and IP addresses to use.

Configuring reverse lookup is required. When you implement reverse lookup, you must define a PTR record on the DNS server so the virtual appliance uses the correct network configuration.

You can use the following sample list of DNS records when you talk to your network administrator. Replace the sample information with information from your environment. This example shows forward DNS records and IP addresses.

Examples of Forward DNS Records and IP Addresses

Domain NameResource TypeIP Address
myworkspaceoneaccess.example.comA10.28.128.3

This example shows reverse DNS records and IP addresses.

Examples of Reverse DNS Records and IP Addresses

IP AddressResource TypeHost Name
10.28.128.3PTRmyworkspaceoneaccess.example.com

After you complete the DNS configuration, verify that the reverse DNS lookup is properly configured. For example, the virtual appliance command host IPaddress must resolve to the DNS name lookup.

Planning for Kerberos Authentication

If you plan to set up Kerberos authentication, note the following conditions:

In a scenario where you use the Omnissa Access connector for Kerberos authentication, the connector host name must match the Active Directory domain to which the connector is joined. For example, if the Active Directory domain is sales.example.com, the connector host name must be connectorhost.sales.example.com.

If you cannot assign a hostname that matches the Active Directory domain structure, you need to configure the connector and Active Directory manually. See the Knowledge Base for information.

Using a Unix/Linux-based DNS Server

If you are using a Unix or Linux-based DNS server and plan to join Omnissa Access to the Active Directory domain, make sure that the appropriate service (SRV) resource records are created for each Active Directory domain controller.

Note: If you have a load balancer with a Virtual IP address (VIP) in front of the DNS servers, note that Omnissa Access does not support using a VIP. You can specify multiple DNS servers separated by a comma.

Was this page helpful?

Provide feedback for this topic

Was this topic helpful?

Please do not include any personal or confidential information.

Generating link…