<?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: Secondry DNS in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167241#M160540</link>
    <description>HI,&lt;BR /&gt;&lt;BR /&gt;Peter is right, but you can also use the domain string in /etc/resolv.conf.&lt;BR /&gt;Check man resolv.conf &lt;BR /&gt;&lt;BR /&gt;Gideon</description>
    <pubDate>Mon, 19 Jan 2004 03:35:43 GMT</pubDate>
    <dc:creator>G. Vrijhoeven</dc:creator>
    <dc:date>2004-01-19T03:35:43Z</dc:date>
    <item>
      <title>Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167239#M160538</link>
      <description>Hi ..&lt;BR /&gt;&lt;BR /&gt;How to configure secondry DNS in my server. Pls Help.</description>
      <pubDate>Mon, 19 Jan 2004 03:28:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167239#M160538</guid>
      <dc:creator>akthar abdul jabbar</dc:creator>
      <dc:date>2004-01-19T03:28:00Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167240#M160539</link>
      <description>edit the /etc/resolv.conf file like next:&lt;BR /&gt;&lt;BR /&gt;search blbla.bla.com&lt;BR /&gt;nameserver &lt;IP first="" server=""&gt;&lt;BR /&gt;nameserver &lt;IP second="" server=""&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Peter&lt;/IP&gt;&lt;/IP&gt;</description>
      <pubDate>Mon, 19 Jan 2004 03:31:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167240#M160539</guid>
      <dc:creator>Hoefnix</dc:creator>
      <dc:date>2004-01-19T03:31:29Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167241#M160540</link>
      <description>HI,&lt;BR /&gt;&lt;BR /&gt;Peter is right, but you can also use the domain string in /etc/resolv.conf.&lt;BR /&gt;Check man resolv.conf &lt;BR /&gt;&lt;BR /&gt;Gideon</description>
      <pubDate>Mon, 19 Jan 2004 03:35:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167241#M160540</guid>
      <dc:creator>G. Vrijhoeven</dc:creator>
      <dc:date>2004-01-19T03:35:43Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167242#M160541</link>
      <description>Do you mean to use a secondary DNS? Then Peter's solution is right.&lt;BR /&gt;If you mean: how do I configure my server to be a secondary DNS, it is more tricky.&lt;BR /&gt;You need to copy your named.conf file from the primary DNS, replace all 'master' entries to 'slave' entries, create the directory used for storing the database files, edit /etc/rc.config.d/namesvrs to start the named, etc.&lt;BR /&gt;&lt;BR /&gt;Before going into more detail on this, explain what you want.</description>
      <pubDate>Mon, 19 Jan 2004 03:37:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167242#M160541</guid>
      <dc:creator>Elmar P. Kolkman</dc:creator>
      <dc:date>2004-01-19T03:37:01Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167243#M160542</link>
      <description>Hi Thanks for quick response,&lt;BR /&gt;&lt;BR /&gt;Do I Need to reboot the server after editing the resolv.conf or it takes effect automatically once I save the file&lt;BR /&gt;&lt;BR /&gt;Akthar</description>
      <pubDate>Mon, 19 Jan 2004 03:41:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167243#M160542</guid>
      <dc:creator>akthar abdul jabbar</dc:creator>
      <dc:date>2004-01-19T03:41:13Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167244#M160543</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;No reboot, it should work right away.&lt;BR /&gt;&lt;BR /&gt;Gideon</description>
      <pubDate>Mon, 19 Jan 2004 03:45:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167244#M160543</guid>
      <dc:creator>G. Vrijhoeven</dc:creator>
      <dc:date>2004-01-19T03:45:38Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167245#M160544</link>
      <description>Hi Elmar,&lt;BR /&gt;&lt;BR /&gt;I want to use secondry DNS address , And I used Peter's suggestion and edited the resolv.conf file .. I have reboot the server or I have to start stop any deamon to take this to effect ??!!&lt;BR /&gt;&lt;BR /&gt;Thanks again for all for useful inputs&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Akthar</description>
      <pubDate>Mon, 19 Jan 2004 03:47:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167245#M160544</guid>
      <dc:creator>akthar abdul jabbar</dc:creator>
      <dc:date>2004-01-19T03:47:05Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167246#M160545</link>
      <description>If you want to test the changes, just swap 1st and 2nd nameserver in the resolv.conf (change the order in the file)and do an nslookup &lt;HOSTNAME in="" dns=""&gt;.&lt;BR /&gt;&lt;BR /&gt;From the response you can figure out which DNS-server is used.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Peter&lt;/HOSTNAME&gt;</description>
      <pubDate>Mon, 19 Jan 2004 03:56:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167246#M160545</guid>
      <dc:creator>Hoefnix</dc:creator>
      <dc:date>2004-01-19T03:56:16Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167247#M160546</link>
      <description>Goodmorning Akhtar (though probably afternoon for you),&lt;BR /&gt;&lt;BR /&gt;If you only want to use a secondary nameserver from the machine, you don't have to reboot. Every time a lookup is done on the server, /etc/resolv.conf is read for the order of DNS servers. Like Peter said you can test it directly.</description>
      <pubDate>Mon, 19 Jan 2004 04:10:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167247#M160546</guid>
      <dc:creator>Elmar P. Kolkman</dc:creator>
      <dc:date>2004-01-19T04:10:47Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167248#M160547</link>
      <description>Just check that you have set /etc/nsswitch.conf to include DNS as an option.</description>
      <pubDate>Mon, 19 Jan 2004 04:40:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167248#M160547</guid>
      <dc:creator>Jakes Louw</dc:creator>
      <dc:date>2004-01-19T04:40:31Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167249#M160548</link>
      <description>If you want to test the changes, just swap to 2nd nameserver in "nslookup" with the command "server".&lt;BR /&gt;Dominique&lt;BR /&gt;</description>
      <pubDate>Mon, 19 Jan 2004 11:02:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167249#M160548</guid>
      <dc:creator>D.Blond</dc:creator>
      <dc:date>2004-01-19T11:02:19Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167250#M160549</link>
      <description>Or you could request the nslookup from a specific DNS server:&lt;BR /&gt;&lt;BR /&gt;nslookup ipaddress dnsserver&lt;BR /&gt;&lt;BR /&gt;eg: nslookup 165.143.128.21 dns2</description>
      <pubDate>Tue, 20 Jan 2004 00:58:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167250#M160549</guid>
      <dc:creator>Jakes Louw</dc:creator>
      <dc:date>2004-01-20T00:58:20Z</dc:date>
    </item>
    <item>
      <title>Re: Secondry DNS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167251#M160550</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Add another line that says "nameserver ip_address" to your /etc/resolv.conf. &lt;BR /&gt;&lt;BR /&gt;DNS will be searched using the servers specified in the order in /etc/resolv.conf. There are couple of points to be noted.&lt;BR /&gt;&lt;BR /&gt;1. As long as the first server responds, secondary name server will not be used.&lt;BR /&gt;2. If the first server does not respond, then the queries will go to next server in the order after the default "retrans" value. The retrans value is 5 seconds.&lt;BR /&gt;3. You can add the configurable parameters retrans and retry to /etc/resolv.conf to set the timeout. retrans is specified in milli seconds. For ex.,&lt;BR /&gt;&lt;BR /&gt;domain yourdomain.com&lt;BR /&gt;nameserver 10.10.10.10&lt;BR /&gt;nameserver 10.10.10.20&lt;BR /&gt;retrans 2000&lt;BR /&gt;retry 2&lt;BR /&gt;&lt;BR /&gt;The above will set the timeout to 2 seconds before the system call queries the next timeout.&lt;BR /&gt;&lt;BR /&gt;4. There is no daemon like 'nscd' in hp-ux that will take care of automatically failing over to the next name server in the resolv.conf file in case the primary server does not respond. So each query has to go through the retrans timeout.&lt;BR /&gt;&lt;BR /&gt;5. nslookup is not a 100% method to test the configuration in /etc/resolv.conf as it doesn't use gethostbyent() calls. But retrans is in effect for all the services that use gethostbyent() set of calls.&lt;BR /&gt;&lt;BR /&gt;-Sri&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 20 Jan 2004 01:28:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/secondry-dns/m-p/3167251#M160550</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2004-01-20T01:28:58Z</dc:date>
    </item>
  </channel>
</rss>

