<?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 Ping strange behaviour in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-strange-behaviour/m-p/2931569#M576876</link>
    <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I have a 11i machine, which I set it to lookup DNS first and then host table, found that if say the entry is in DNS, both nslookup and ping get very fast result, however, when the host is not in DNS but only in /etc/hosts , the nslookup still fine but the ping will get long delay ( ~10sec ) before it giving out the result, any body know why? &lt;BR /&gt;&lt;BR /&gt;Gordon</description>
    <pubDate>Thu, 20 Mar 2003 02:25:21 GMT</pubDate>
    <dc:creator>Gordon_3</dc:creator>
    <dc:date>2003-03-20T02:25:21Z</dc:date>
    <item>
      <title>Ping strange behaviour</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-strange-behaviour/m-p/2931569#M576876</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I have a 11i machine, which I set it to lookup DNS first and then host table, found that if say the entry is in DNS, both nslookup and ping get very fast result, however, when the host is not in DNS but only in /etc/hosts , the nslookup still fine but the ping will get long delay ( ~10sec ) before it giving out the result, any body know why? &lt;BR /&gt;&lt;BR /&gt;Gordon</description>
      <pubDate>Thu, 20 Mar 2003 02:25:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-strange-behaviour/m-p/2931569#M576876</guid>
      <dc:creator>Gordon_3</dc:creator>
      <dc:date>2003-03-20T02:25:21Z</dc:date>
    </item>
    <item>
      <title>Re: Ping strange behaviour</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-strange-behaviour/m-p/2931570#M576877</link>
      <description>Check you nsswitch.conf file to see if it points to the DNS and then files.  If DNS then a failure is returned after a failed lookup and before the host file is queried.  This would explain some latency.</description>
      <pubDate>Thu, 20 Mar 2003 02:29:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-strange-behaviour/m-p/2931570#M576877</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2003-03-20T02:29:35Z</dc:date>
    </item>
    <item>
      <title>Re: Ping strange behaviour</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-strange-behaviour/m-p/2931571#M576878</link>
      <description>I would solve the problem by putting files first.  Why bother with DNS if the IP addy you want is in the /etc/hosts file?&lt;BR /&gt;&lt;BR /&gt;The delay is more than likely due to the fact that ping does have to look up the IP and make it thru all the DNS servers before it goes to /etc/hosts.  Even though the nslookup is fine, I would almost bet the delay with ping is during the resolving of host to IP addy.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Mar 2003 02:31:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-strange-behaviour/m-p/2931571#M576878</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2003-03-20T02:31:47Z</dc:date>
    </item>
    <item>
      <title>Re: Ping strange behaviour</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-strange-behaviour/m-p/2931572#M576879</link>
      <description>It's because nslookup (as a testtool) doesn't have the same resolver routines as do utilities like ping, telnet, ftp, et. al. &lt;BR /&gt;&lt;BR /&gt;You need to edit /etc/nsswitch.conf and adjust it to suit your needs. Generally the best performance results if a few very frequently used and very seldomly changed hosts are found in /etc/hosts. When NOTFOUND then go to DNS.&lt;BR /&gt;&lt;BR /&gt;The other preference (and generally easier but slightly slower) is to let DNS maintain every host except loopback and the local hostname BUT you must then make sure that you have a robust DNS service with slave servers.</description>
      <pubDate>Thu, 20 Mar 2003 02:36:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-strange-behaviour/m-p/2931572#M576879</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2003-03-20T02:36:20Z</dc:date>
    </item>
  </channel>
</rss>

