<?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 for stand alone database server in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-for-stand-alone-database-server/m-p/2852602#M579569</link>
    <description>Hi Doug,&lt;BR /&gt;&lt;BR /&gt;For lightning-fast response, I would also recommend setting up your server as either a caching-only nameserver or a stealth secondary for your zones.  You would then list the server itself as the first resolver.  We do this with our high-volume SMTP servers, and it improves performance considerably.&lt;BR /&gt;&lt;BR /&gt;It also ensures that DNS changes are propagated to your server instead of having to maintain static records in /etc/hosts.  Depending on the size of your environment, though, it may be easier just to do like Clay noted and put the commonly resolved names in /etc/hosts.  And like Clay noted, you should have at a minimum localhost and your machine's own name in /etc/hosts.&lt;BR /&gt;&lt;BR /&gt;If you don't go with caching-only or stealth secondary, note that you should probably list files first then dns in /etc/nsswitch.conf.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Jim</description>
    <pubDate>Tue, 26 Nov 2002 20:46:38 GMT</pubDate>
    <dc:creator>Jim Turner</dc:creator>
    <dc:date>2002-11-26T20:46:38Z</dc:date>
    <item>
      <title>DNS for stand alone database server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-for-stand-alone-database-server/m-p/2852600#M579567</link>
      <description>I am unsure if I should be posting here or in the sysadmin...&lt;BR /&gt;&lt;BR /&gt;I have a 11.00 database and app server that I want to have the ability to resolve dns.  Right now the dns local name server and dns resolver values are empty.  We use novell dns for our network.  &lt;BR /&gt;I am assuming I need to add the novell dns server to the dns resolver field.  What else do I need to do?  Are there entries in nsswitchlconf or hosts or resolv.conf.  &lt;BR /&gt;Recommendations on the order of nss?  &lt;BR /&gt;&lt;BR /&gt;TIA&lt;BR /&gt;Doug</description>
      <pubDate>Tue, 26 Nov 2002 17:24:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-for-stand-alone-database-server/m-p/2852600#M579567</guid>
      <dc:creator>Doug_3</dc:creator>
      <dc:date>2002-11-26T17:24:05Z</dc:date>
    </item>
    <item>
      <title>Re: DNS for stand alone database server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-for-stand-alone-database-server/m-p/2852601#M579568</link>
      <description>I would have a small /etc/hosts files with the local host, loopback, and a few often accessed hosts in it. You then set /etc/resolv.conf to your DNS server. My order for /etc/nsswitch.conf would be FILES then DNS.&lt;BR /&gt;</description>
      <pubDate>Tue, 26 Nov 2002 17:35:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-for-stand-alone-database-server/m-p/2852601#M579568</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-11-26T17:35:51Z</dc:date>
    </item>
    <item>
      <title>Re: DNS for stand alone database server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dns-for-stand-alone-database-server/m-p/2852602#M579569</link>
      <description>Hi Doug,&lt;BR /&gt;&lt;BR /&gt;For lightning-fast response, I would also recommend setting up your server as either a caching-only nameserver or a stealth secondary for your zones.  You would then list the server itself as the first resolver.  We do this with our high-volume SMTP servers, and it improves performance considerably.&lt;BR /&gt;&lt;BR /&gt;It also ensures that DNS changes are propagated to your server instead of having to maintain static records in /etc/hosts.  Depending on the size of your environment, though, it may be easier just to do like Clay noted and put the commonly resolved names in /etc/hosts.  And like Clay noted, you should have at a minimum localhost and your machine's own name in /etc/hosts.&lt;BR /&gt;&lt;BR /&gt;If you don't go with caching-only or stealth secondary, note that you should probably list files first then dns in /etc/nsswitch.conf.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Jim</description>
      <pubDate>Tue, 26 Nov 2002 20:46:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dns-for-stand-alone-database-server/m-p/2852602#M579569</guid>
      <dc:creator>Jim Turner</dc:creator>
      <dc:date>2002-11-26T20:46:38Z</dc:date>
    </item>
  </channel>
</rss>

