Consider the scenario where OES server is present in one DNS domain and AD server is present in another DNS domain. Before joining OES to AD domain, do the following:
Ensure to meet the NSS AD requirements. For more information, see Prerequisites for Installing and Configuring NSS AD in the OES 2018 SP3: Installation Guide.
The OES server should be able to resolve the DNS queries for the AD domain.
The example provides how to successfully join OES server to AD domain when OES and AD servers are in two different domains:
OES server is in oesdomain.com with the DNS server IP address 192.168.1.2
AD server is joined to addomain.com with the DNS server IP address 192.168.20.22
The DNS server with the IP address 192.168.1.2 should resolve the DNS queries on addomain.com. There are different ways to resolve the DNS queries, we have considered using DNS forwarder in this example:
Configure the forwarder on 192.168.1.2 that points to 192.168.20.22
Ensure all the PTR records exists for all Domain Controller (DC) and Global Catalog (GC) in 192.168.20.22
From the OES server console, verify if the AD DC server and AD domain is resolvable.
nslookup adserver1.addomain.com
nslookup addomain.com
The command should execute successfully and display details of the AD server and domain.
NOTE:For FTP AD remote navigation, ensure that the search attribute present in /etc/resolv.conf is configured with all the AD domain entries of the OES servers.