DNS Host name Resolution

[Stephen Jones_3]

I'm having a few problems getting discovered hosts displaying the correct system name. SIM will only display the IP address of the host.

DNS resolution is working correctly, but the hosts in question do have multiple dns entries, which reference different names.

I've tried importing host files to get the system names correct, but it always goes back to display it in IP form.

In IM7 it was possible to edit systems to display the correct name. I've search through SIM and this feature, even through the comand prompt doesn't seem available.

Any help would be greatly recieved.
Regards,
Stephen

[James Kennedy_4]

Talk about a pain, I'm having similar issues. I can ping the name of the server, by name, fine from the SIM server. But it just wont resolve the device by name in SIM and lists by IP Address. I've tried everything I can think of. I even manually edited the database entries for the device, it stayed for about a day, then returned to just an IP Address. I miss how in IM7 you could atleast modify it manually.

I have a similar problem with a cluster. SIM seems seems to think my Virtual Cluster is a server and the Node is a Cluster and it's backwards and there's no way to change it manually.

[David Claypool]

This usually indicates a Reverse DNS problem. You may still be able to ping by name, but in Windows try 'ping -a xx.xx.xx.xx' so that Windows tries to resolve the name. If it can't, you have a reverse DNS problem.

You can supply hosts entries to hpSIM by going to Options --> Manual or Automatic Discovery --> Hosts file page

[Stephen Jones_3]

a manual nslookup ***.***.***.*** on the SIMS server returns the name correctly.

Having added the correctly formatted host file manually to SIMS it displays the host by it's IP address.

[dospavlos]

I had this problem which was the result of not having a reverse dns entry on the Unix side. My question to HP is this: What if I have a reverse dns entry matching the ip to something other than the server name? This type of entry, in my case, is needed for url resolution. What's the fix for this?? When is the functionality to manually edit the name going to be available. This type of setup also results in the software status never registering.

[Josh Stacey]

Like the other "victims" of the new version of SIM, I am experiencing the same resolution issue - with inability to manually edit the names, thus correcting the issue. In my case, I was performing software updates against a few hundred machines (a handful of which were incorrectly resolving). As a temporary fix, I put a local host file on the SIM server that included the name to IP mappings of the unresolved machines. Just an idea for you to toy with (while HP fixes this bug). This of course assumes that you are using static IP addresses as opposed to DHCP. Obviously, this is a hack, but it gets the job done while HP "works out the kinks".

Thanks - Josh

[Rob Buxton]

By making sure that the DNS for both sides was correct I have got my Servers to identify themselves correctly.

As others have noted you need Reverse Lookups.
Also they need to correlate with the forward lookups.
Here we are a mix of AD and Unix based DNS. We're slowly mving to new sub-domains.
What I found was that if you had an entry for n.n.n.n pointing to server.myco.com, but the server in the forward lookup was server.subdomain.myco.com then IM would not use the name.

SIM uses only DNS to cerify the name as this is common to OSes. It seems to want to make very sure that it has the correct name before it uses it.

At this point I don't see where there's a bug that needs to be fixed. We have a DNS that is far from standard, but it has been made to correctly identify the devices for SIM.