<?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: Setting Up A Caching DNS Server On A Private Network in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/setting-up-a-caching-dns-server-on-a-private-network/m-p/3777245#M83797</link>
    <description>Hi there --&lt;BR /&gt;&lt;BR /&gt;I have done some configuration and according to the /etc/init.d/named status command, the server is running. However, when I do an nslookup command on any of the servers, I get the error ;; connection timed out; no servers could be reached. &lt;BR /&gt;&lt;BR /&gt;I am enclosing a copy of the named.conf file for your perusal. &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 25 Apr 2006 10:19:57 GMT</pubDate>
    <dc:creator>Andrew Kaplan</dc:creator>
    <dc:date>2006-04-25T10:19:57Z</dc:date>
    <item>
      <title>Setting Up A Caching DNS Server On A Private Network</title>
      <link>https://community.hpe.com/t5/operating-system-linux/setting-up-a-caching-dns-server-on-a-private-network/m-p/3777243#M83795</link>
      <description>Hi there --&lt;BR /&gt;&lt;BR /&gt;I have completed downloading the BIND software onto a system that will server as the DNS server, and I am now ready to configure the it. The type of server I want to create is a caching server. The reason for this is I want the system to resolve hostnames exclusively within a private network, 192.168.0.x, and the server will NOT have access to the Internet. I know I will need to modify the /etc/named.conf and other files but I am not familiar with what settings are needed. What tools and/or entries can I use to complete the configuration of the server? Thanks. &lt;BR /&gt;</description>
      <pubDate>Tue, 25 Apr 2006 08:51:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/setting-up-a-caching-dns-server-on-a-private-network/m-p/3777243#M83795</guid>
      <dc:creator>Andrew Kaplan</dc:creator>
      <dc:date>2006-04-25T08:51:30Z</dc:date>
    </item>
    <item>
      <title>Re: Setting Up A Caching DNS Server On A Private Network</title>
      <link>https://community.hpe.com/t5/operating-system-linux/setting-up-a-caching-dns-server-on-a-private-network/m-p/3777244#M83796</link>
      <description>You don't want a caching server in this case.&lt;BR /&gt;You need a full server with listing for&lt;BR /&gt;your 192.168.0.*.* network.  You will &lt;BR /&gt;need to do forward and backward listing.&lt;BR /&gt;&lt;BR /&gt;There is no official top level domain for &lt;BR /&gt;private networks.  I use LCL or PRI, or just&lt;BR /&gt;drop the top level all together. &lt;BR /&gt;&lt;BR /&gt;Look at the bind howto at TLDP.org.  Skip&lt;BR /&gt;the section on root servers. You will be &lt;BR /&gt;the root server.&lt;BR /&gt;&lt;BR /&gt;As an alternative to bind you may want to&lt;BR /&gt;look at DNSMasq which is simpler to configure.  You just need to create a &lt;BR /&gt;/etc/hosts file.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 25 Apr 2006 09:37:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/setting-up-a-caching-dns-server-on-a-private-network/m-p/3777244#M83796</guid>
      <dc:creator>Bill Thorsteinson</dc:creator>
      <dc:date>2006-04-25T09:37:04Z</dc:date>
    </item>
    <item>
      <title>Re: Setting Up A Caching DNS Server On A Private Network</title>
      <link>https://community.hpe.com/t5/operating-system-linux/setting-up-a-caching-dns-server-on-a-private-network/m-p/3777245#M83797</link>
      <description>Hi there --&lt;BR /&gt;&lt;BR /&gt;I have done some configuration and according to the /etc/init.d/named status command, the server is running. However, when I do an nslookup command on any of the servers, I get the error ;; connection timed out; no servers could be reached. &lt;BR /&gt;&lt;BR /&gt;I am enclosing a copy of the named.conf file for your perusal. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 25 Apr 2006 10:19:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/setting-up-a-caching-dns-server-on-a-private-network/m-p/3777245#M83797</guid>
      <dc:creator>Andrew Kaplan</dc:creator>
      <dc:date>2006-04-25T10:19:57Z</dc:date>
    </item>
    <item>
      <title>Re: Setting Up A Caching DNS Server On A Private Network</title>
      <link>https://community.hpe.com/t5/operating-system-linux/setting-up-a-caching-dns-server-on-a-private-network/m-p/3777246#M83798</link>
      <description>take a look at djbdns/tinydns instead of bind for this purpose.  Smaller, easier to configure, and better suited for your specific purpose.</description>
      <pubDate>Wed, 26 Apr 2006 09:23:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/setting-up-a-caching-dns-server-on-a-private-network/m-p/3777246#M83798</guid>
      <dc:creator>Alan_152</dc:creator>
      <dc:date>2006-04-26T09:23:51Z</dc:date>
    </item>
    <item>
      <title>Re: Setting Up A Caching DNS Server On A Private Network</title>
      <link>https://community.hpe.com/t5/operating-system-linux/setting-up-a-caching-dns-server-on-a-private-network/m-p/3777247#M83799</link>
      <description>You configuration file seems to be good, try using dig:&lt;BR /&gt;&lt;BR /&gt;dig @ip_of_dns_server &lt;A href="http://www.hp.com" target="_blank"&gt;www.hp.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Post the results. Check your /etc/resolv.conf file, it should be like this:&lt;BR /&gt;&lt;BR /&gt;domain example.com&lt;BR /&gt;nameserver 127.0.0.1</description>
      <pubDate>Wed, 26 Apr 2006 10:00:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/setting-up-a-caching-dns-server-on-a-private-network/m-p/3777247#M83799</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-04-26T10:00:32Z</dc:date>
    </item>
  </channel>
</rss>

