<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DNS error with Discovery in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/dns-error-with-discovery/m-p/4778199#M43573</link>
    <description>I would try an ipconfig /flushdns on the CMS server and followed by an identify system. &lt;BR /&gt;&lt;BR /&gt;In bigger environments check the domain search option. nslookup MyCMS and  Ip -&amp;gt; Nodename gives you something like MyCMS.mydomain.com &lt;BR /&gt;nslookup MyCMS.mydomain.com should you tell the same adress and more important the hostname should be also the same name.&lt;BR /&gt;&lt;BR /&gt;Sometime you can get very strange response if the system has multiple NIC's.</description>
    <pubDate>Sat, 16 Apr 2011 18:21:39 GMT</pubDate>
    <dc:creator>BPE</dc:creator>
    <dc:date>2011-04-16T18:21:39Z</dc:date>
    <item>
      <title>DNS error with Discovery</title>
      <link>https://community.hpe.com/t5/server-management-systems/dns-error-with-discovery/m-p/4778198#M43572</link>
      <description>I'm running SIM 6.2. When I run a Discovery and enter the ip address the job runs but reports minor errors "...However, the forward DNS lookup was not successful because HP SIM could not get the fully qualified  domain name for the system being discovered..." If I try nslookup from the CMS server both forward and reverse lookups resolve fine. Also, if I select the server and run Identify System the name resolves fine. So, how do I get the initial discovery to resolve the name ?</description>
      <pubDate>Sat, 16 Apr 2011 01:14:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/dns-error-with-discovery/m-p/4778198#M43572</guid>
      <dc:creator>pz7rx8</dc:creator>
      <dc:date>2011-04-16T01:14:19Z</dc:date>
    </item>
    <item>
      <title>Re: DNS error with Discovery</title>
      <link>https://community.hpe.com/t5/server-management-systems/dns-error-with-discovery/m-p/4778199#M43573</link>
      <description>I would try an ipconfig /flushdns on the CMS server and followed by an identify system. &lt;BR /&gt;&lt;BR /&gt;In bigger environments check the domain search option. nslookup MyCMS and  Ip -&amp;gt; Nodename gives you something like MyCMS.mydomain.com &lt;BR /&gt;nslookup MyCMS.mydomain.com should you tell the same adress and more important the hostname should be also the same name.&lt;BR /&gt;&lt;BR /&gt;Sometime you can get very strange response if the system has multiple NIC's.</description>
      <pubDate>Sat, 16 Apr 2011 18:21:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/dns-error-with-discovery/m-p/4778199#M43573</guid>
      <dc:creator>BPE</dc:creator>
      <dc:date>2011-04-16T18:21:39Z</dc:date>
    </item>
    <item>
      <title>Re: DNS error with Discovery</title>
      <link>https://community.hpe.com/t5/server-management-systems/dns-error-with-discovery/m-p/4778200#M43574</link>
      <description>The multiple nics seems to be the culprit. I set up the other nics with the same DNS entries and everthing is wokin fine now.</description>
      <pubDate>Sun, 17 Apr 2011 17:06:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/dns-error-with-discovery/m-p/4778200#M43574</guid>
      <dc:creator>pz7rx8</dc:creator>
      <dc:date>2011-04-17T17:06:38Z</dc:date>
    </item>
  </channel>
</rss>

