This article is about Linux network/DNS configuration.
If Orion is part of a domain, host names may not be resolved correctly, which could lead to synchronization issues between VMan and VIM.
If Virtualization Manager does not use automatic network configuration (DHCP), then the search domain must be specified in the /etc/resolv.conf file to be able to use short domain names as datasource addresses.
If DHCP is used, the DNS servers and the search domain is filled automatically, and the content of this configuration file can be overwritten with data received from the DHCP server.
Consider the following example:
If a host named "esxhost1" is in the "example.com" domain, then the full domain name is "esxhost1.example.com".
If you have the search domain specified in /etc/resolv.conf, then you can use "esxhost1" as an address because it will be resolved to the same IP address as the "esxhost1.example.com" full domain name.
In some cases, if Orion is running in the "example.com" domain, it will only store the host name of the ESX or Hyper-V host in its short form. If the short form is used in Orion, this will prevent the VMan-VIM integration from mapping the entity correctly when the full domain name is used in VMan, because the "esxhost1" name that is stored in Orion does not equal the "esxhost1.example.com" name that is stored in Virtualization Manager.
To be able to use short names as datasource address, modify the /etc/resolv.conf file:
Repeat these steps for every domain you want to have as search domain.
This way, when the DNS client is presented with a host name, it will apply every search domain provided in the /etc/resolv.conf file to resolve the host name, in the order you added them.
You can achieve the same result for a small amount of selected servers. You can directly map a name to an IP address in the /etc/hosts file to map the short name of the server to an IP address.