NetIQ AppManager 7.0.x
Servers in the Operator Console cannot be renamed.
If a machine was added to the operator console with an IP address, and you wanted to change it to the hostname, you will need to remove the machine with the IP address from the operator console. Then add it back with the hostname.
If the hostname is not resolvable, then use either a LMHOST file or a HOSTS file on the Management Server when adding the machine.
The following procedure is designed to correct numerous obscure DNS errors the first time:
1. Verify every domain controller's IP addresses in the DNS forward lookup zone(s). In addition, make sure there are no missing or old (unneeded) host records. Pay particular attention to the global catalog _gc records in the forest root domain's forward lookup zone located under _tcp.
2. verify every domain controller's IP addresses in the DNS reverse lookup zone(s). In addition, make sure there are no missing old (unneeded) reverse pointer records.
3. at the primary DNS server, bounce the DNS server service and DNS client service in that order
4. at the secondary DNS server, bounce the DNS server service and DNS client service in that order
5. at each domain controller that is not the primary or secondary DNS server and is not deliberately intended to be a DNS server, stop the DNS Server service (if it is present) and disable it
6. at each domain controller that is not the primary or secondary DNS server and is not deliberately intended to be a DNS server, bounce the DNS client service
7. Use nslookup at the primary and secondary DNS servers to verify that the DMA console machine's hostname and IP address are both resolved properly as follows:
nslookup <IP address>
8. Use nslookup at the Operator Console machine to verify at minimum that the primary and secondary DNS servers, the domain GC catalog server(s), and all five FSMO role servers are properly resolved for both hostname and IP address as follows:
nslookup <IP address>
9. At the Operator Console machine, query the domain SRV (service locator) records as follows:
where <domain.suffix> = the domain name, such as "microsoft.com". Verify the displayed information is correct. If not, make corrections as necessary to the dc records located under the domain's forward lookup zone.
This issue can also be caused by an incorrect static entry in the LMHOSTS file.