DNS RFC 2317 support

Russ Todd — Tue, 15 Feb 2011 17:32:53 GMT

I have many systems that are not resolving properly and only returning IP addresses instead of system names.

When I perform a discovery or a identify systems i eventually get the error message:

Major: The name of the system could not be resolved to a fully qualified
DNS name. For a Windows CMS, make sure that the domain name of the
managed system is added to the DNS suffixes in the Windows Advanced
TCP/IP Settings page.
Major: The reverse DNS lookup using the IP address returns
vc-sj.corp.adobe.com. However, the forward DNS lookup was not
successful because HP SIM could not get the fully qualified DNS
name for the system being discovered. In HP SIM, the fully
qualified DNS name for the system will be empty. Verify that the
system name is in the forward lookup table in the DNS server
configuration.

The DNS team indicates that the only difference for the subnets that theys systems are on is that they have implemented a scheme based on the RFC 2317.

When I perform a nslookup in these machines, it returns the information one would expect, and additional information.

#1. is there a way to see how sim is parsing the nslookup to see where the trouble is?

#2 is the support for this RFC?

#3 is there any tweeks that can be applied?

The Sim server is Windows 2008 R2, running SIM 6.1

Re: DNS RFC 2317 support

David Claypool — Tue, 15 Feb 2011 17:48:34 GMT

You can check the resolution that HP SIM is seeing with mxgethostname. http://www.hp.com/go/hpsim --> Information Library --> mxgethostname.1m

topic Re: DNS RFC 2317 support in Server Management - Systems Insight Manager

DNS RFC 2317 support

Re: DNS RFC 2317 support