<?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: RHEL dns in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/rhel-dns/m-p/4797392#M44507</link>
    <description>On RHEL 5 and newer, by running "yum install caching-nameserver". This will give you the BIND name server daemon with an example configuration as "/etc/named.caching-nameserver.conf". &lt;BR /&gt;&lt;BR /&gt;Copy the example configuration to /etc/named.conf. If you don't want (or aren't allowed) to use Internet root nameservers directly, you should add a few options to the configuration file to define the local nameservers your caching DNS server will use to get the data that is not already in the cache. For example, if your site's DNS servers are 1.2.3.4 and 5.6.7.8, add these lines to the "options {" section of the configuration file:&lt;BR /&gt;&lt;BR /&gt;forwarders { 1.2.3.4; 5.6.7.8; }; &lt;BR /&gt;forward only;&lt;BR /&gt;&lt;BR /&gt;If you want to try the configured forwarders first, but fall back to contacting the Internet nameservers directly if the forwarder servers aren't responding, replace "forward only" with "forward first".&lt;BR /&gt;&lt;BR /&gt;After creating your /etc/named.conf, run:&lt;BR /&gt;&lt;BR /&gt;chkconfig named on&lt;BR /&gt;service named start &lt;BR /&gt;&lt;BR /&gt;Use "nslookup &lt;SOME dns="" name=""&gt; 127.0.0.1" or "dig &lt;SOME dns="" name=""&gt; @127.0.0.1" to make sure your caching DNS server works, then change the "nameserver" line(s) in /etc/resolv.conf to point to 127.0.0.1.&lt;BR /&gt;You're done!&lt;BR /&gt;&lt;BR /&gt;MK&lt;/SOME&gt;&lt;/SOME&gt;</description>
    <pubDate>Thu, 09 Jun 2011 16:50:16 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2011-06-09T16:50:16Z</dc:date>
    <item>
      <title>RHEL dns</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel-dns/m-p/4797391#M44506</link>
      <description>How would you implement a dns as a cachee instance running local on a server to avoid huge dns lookups?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Mike&lt;BR /&gt;</description>
      <pubDate>Thu, 09 Jun 2011 13:56:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel-dns/m-p/4797391#M44506</guid>
      <dc:creator>MSwift</dc:creator>
      <dc:date>2011-06-09T13:56:22Z</dc:date>
    </item>
    <item>
      <title>Re: RHEL dns</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rhel-dns/m-p/4797392#M44507</link>
      <description>On RHEL 5 and newer, by running "yum install caching-nameserver". This will give you the BIND name server daemon with an example configuration as "/etc/named.caching-nameserver.conf". &lt;BR /&gt;&lt;BR /&gt;Copy the example configuration to /etc/named.conf. If you don't want (or aren't allowed) to use Internet root nameservers directly, you should add a few options to the configuration file to define the local nameservers your caching DNS server will use to get the data that is not already in the cache. For example, if your site's DNS servers are 1.2.3.4 and 5.6.7.8, add these lines to the "options {" section of the configuration file:&lt;BR /&gt;&lt;BR /&gt;forwarders { 1.2.3.4; 5.6.7.8; }; &lt;BR /&gt;forward only;&lt;BR /&gt;&lt;BR /&gt;If you want to try the configured forwarders first, but fall back to contacting the Internet nameservers directly if the forwarder servers aren't responding, replace "forward only" with "forward first".&lt;BR /&gt;&lt;BR /&gt;After creating your /etc/named.conf, run:&lt;BR /&gt;&lt;BR /&gt;chkconfig named on&lt;BR /&gt;service named start &lt;BR /&gt;&lt;BR /&gt;Use "nslookup &lt;SOME dns="" name=""&gt; 127.0.0.1" or "dig &lt;SOME dns="" name=""&gt; @127.0.0.1" to make sure your caching DNS server works, then change the "nameserver" line(s) in /etc/resolv.conf to point to 127.0.0.1.&lt;BR /&gt;You're done!&lt;BR /&gt;&lt;BR /&gt;MK&lt;/SOME&gt;&lt;/SOME&gt;</description>
      <pubDate>Thu, 09 Jun 2011 16:50:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rhel-dns/m-p/4797392#M44507</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2011-06-09T16:50:16Z</dc:date>
    </item>
  </channel>
</rss>

