<?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 nslookup in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/nslookup/m-p/2546579#M595388</link>
    <description>On a 10.20 c110 box, when I enter nslookup, I get # nslookup&lt;BR /&gt;*** Can't find server name for address 192.168.1.2: Non-existent domain&lt;BR /&gt;*** Default servers are not available&lt;BR /&gt;Using /etc/hosts on:  fredin&lt;BR /&gt;&lt;BR /&gt;What is the problem with DNS that is not allowing it to resolve the inquery?</description>
    <pubDate>Thu, 28 Jun 2001 18:54:41 GMT</pubDate>
    <dc:creator>Bill Pontius</dc:creator>
    <dc:date>2001-06-28T18:54:41Z</dc:date>
    <item>
      <title>nslookup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nslookup/m-p/2546579#M595388</link>
      <description>On a 10.20 c110 box, when I enter nslookup, I get # nslookup&lt;BR /&gt;*** Can't find server name for address 192.168.1.2: Non-existent domain&lt;BR /&gt;*** Default servers are not available&lt;BR /&gt;Using /etc/hosts on:  fredin&lt;BR /&gt;&lt;BR /&gt;What is the problem with DNS that is not allowing it to resolve the inquery?</description>
      <pubDate>Thu, 28 Jun 2001 18:54:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nslookup/m-p/2546579#M595388</guid>
      <dc:creator>Bill Pontius</dc:creator>
      <dc:date>2001-06-28T18:54:41Z</dc:date>
    </item>
    <item>
      <title>Re: nslookup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nslookup/m-p/2546580#M595389</link>
      <description>Check Nsswitch.conf in etc . You will find entry for DNS to look first etc/hosts or DNS files. Change it for DNS then to look for /etc/hosts file&lt;BR /&gt;Hope this helps</description>
      <pubDate>Thu, 28 Jun 2001 19:06:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nslookup/m-p/2546580#M595389</guid>
      <dc:creator>Uday_S_Ankolekar</dc:creator>
      <dc:date>2001-06-28T19:06:45Z</dc:date>
    </item>
    <item>
      <title>Re: nslookup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nslookup/m-p/2546581#M595390</link>
      <description>You might also check your /etc/resolv.conf file to make sure that your domain name and nameservers are specified correctly.&lt;BR /&gt;</description>
      <pubDate>Thu, 28 Jun 2001 19:09:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nslookup/m-p/2546581#M595390</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2001-06-28T19:09:04Z</dc:date>
    </item>
    <item>
      <title>Re: nslookup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nslookup/m-p/2546582#M595391</link>
      <description>Bill,&lt;BR /&gt;&lt;BR /&gt;1.  Make sure your /etc/hosts file has your machine's hostname and IP address listed correctly.  Both should agree with what you have in /etc/rc.config.d/netconf for hostname and IP address.&lt;BR /&gt;&lt;BR /&gt;2.  Make sure your /etc/resolv.conf file has the following entries:&lt;BR /&gt;domain foo.com&lt;BR /&gt;nameserver 1.2.3.4&lt;BR /&gt;nameserver 5.6.7.7&lt;BR /&gt;where "foo.com" is your domain, and the nameserver(s) identified (max=3) are actually legitimate nameservers that are authoritative for your domain.&lt;BR /&gt;&lt;BR /&gt;3.  Make sure your /etc/nsswitch.conf file specifies DNS first (if that's what you want) then /etc/hosts.  The contents of the file should look similar to this:&lt;BR /&gt;hosts: dns[NOTFOUND=continue UNAVAIL=continue] files[NOTFOUND=return UNAVAIL=return]&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Jim</description>
      <pubDate>Thu, 28 Jun 2001 19:16:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nslookup/m-p/2546582#M595391</guid>
      <dc:creator>Jim Turner</dc:creator>
      <dc:date>2001-06-28T19:16:16Z</dc:date>
    </item>
    <item>
      <title>Re: nslookup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nslookup/m-p/2546583#M595392</link>
      <description>Actualy, this is a common problem with nslookup.  When it is told to use DNS first, it will ask the IP address of DNS server: what is your name?  Amazingly enough, many DNS administrators forget to give their server a name and enter it into the DNS database.  In other words, the DNS server does not know it's own name.&lt;BR /&gt;&lt;BR /&gt;One could argue that this is a security feature, that it prevents IP address spoofing. &lt;BR /&gt;&lt;BR /&gt;So the fix is either: get your DNS server updated to report its hostname when queried about the IP address (reverse lookup). &lt;BR /&gt;&lt;BR /&gt;Or, change your search policy as mentioned before to use hosts first.  The latter is definitely preferred for network efficiency as well as speed.  Put the most common IP addresses in your hosts file.  The nslookup will use the server for everything else.</description>
      <pubDate>Thu, 28 Jun 2001 21:35:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nslookup/m-p/2546583#M595392</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2001-06-28T21:35:43Z</dc:date>
    </item>
  </channel>
</rss>

