<?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 First Name server not responding in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/first-name-server-not-responding/m-p/2422748#M278</link>
    <description>I have three nameserver line in resolv.conf. When first server goes down it waits for around 80Sec and gets the answer from second server. But when I do nslookup again it still trys the first nameserver. &lt;BR /&gt;If I am not mistaken, if first server not respond it should ask second server then second querie it should not ask first server again.&lt;BR /&gt;Does I need any extra step?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Sachin</description>
    <pubDate>Tue, 09 May 2000 18:19:05 GMT</pubDate>
    <dc:creator>Sachin Patel</dc:creator>
    <dc:date>2000-05-09T18:19:05Z</dc:date>
    <item>
      <title>First Name server not responding</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/first-name-server-not-responding/m-p/2422748#M278</link>
      <description>I have three nameserver line in resolv.conf. When first server goes down it waits for around 80Sec and gets the answer from second server. But when I do nslookup again it still trys the first nameserver. &lt;BR /&gt;If I am not mistaken, if first server not respond it should ask second server then second querie it should not ask first server again.&lt;BR /&gt;Does I need any extra step?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Sachin</description>
      <pubDate>Tue, 09 May 2000 18:19:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/first-name-server-not-responding/m-p/2422748#M278</guid>
      <dc:creator>Sachin Patel</dc:creator>
      <dc:date>2000-05-09T18:19:05Z</dc:date>
    </item>
    <item>
      <title>Re: First Name server not responding</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/first-name-server-not-responding/m-p/2422749#M279</link>
      <description>Sachin,&lt;BR /&gt;&lt;BR /&gt;To the best of my knowledge, your nslookup will consistantly query the first name server until you change your resolve.conf file to do otherwise.&lt;BR /&gt;&lt;BR /&gt;Your HP-UX system doesn't know when the 1st name server will be back up again, and will therefore continue to query it.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Andrew</description>
      <pubDate>Tue, 09 May 2000 22:50:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/first-name-server-not-responding/m-p/2422749#M279</guid>
      <dc:creator>Andrew_4</dc:creator>
      <dc:date>2000-05-09T22:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: First Name server not responding</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/first-name-server-not-responding/m-p/2422750#M280</link>
      <description>There are other keywords you can use in nsswitch.conf&lt;BR /&gt;&lt;BR /&gt;i.e&lt;BR /&gt;&lt;BR /&gt;dns [NOTFOUND=continue TRYAGAIN=continue]&lt;BR /&gt;&lt;BR /&gt;you might want to use some of these</description>
      <pubDate>Mon, 15 May 2000 05:39:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/first-name-server-not-responding/m-p/2422750#M280</guid>
      <dc:creator>Anthony Goonetilleke</dc:creator>
      <dc:date>2000-05-15T05:39:14Z</dc:date>
    </item>
  </channel>
</rss>

