[no subject]

> Also, I seem to remember reading in one of the tldp.org
> how-to's on dns - they mention split dns and how to
> configure. 
> 
&gt; <a  rel="nofollow" href="http://www.etherboy.com/dns/chrootdns.html";>http://www.etherboy.com/dns/chrootdns.html</a>
&gt; <a  rel="nofollow" href="http://tldp.org/HOWTO/DNS-HOWTO-10.html";>http://tldp.org/HOWTO/DNS-HOWTO-10.html</a> - bottom of the
&gt; page, is where I found the link.

It's actually really easy to do split DNS. A simple example is something
like:

view &quot;internal&quot; {
	// here I'm assuming you already have an ACL defined
	// called &quot;internal-addresses&quot;
        match-clients { internal-addresses; };

	// now add your zones, like:
        zone &quot;localhost&quot; IN {
                type master;
                file &quot;internal/localhost.zone&quot;;
        };
};

view &quot;external&quot; {
	// here I'm assuming you already have an ACL defined
        match-clients { any; };

	// now add your zones, like:
	zone &quot;example.com&quot; IN {
		type master;
		file &quot;external/example.com.zone&quot;;
	};
};

The basic logic is that you define an ACL to match your inside hosts. Then,
anything that matches that ACL gets served from the &quot;internal&quot; view.  
Everyone, regardless of IP, gets served from the &quot;external&quot; view. With that
scenario, you'd put your public info in the external view, and your
internal-only in the internal view.

You can, of course, get more sophisticated and use non-wild-card ACLs to
create multiple different views.  You can also do things like have 
multiple views providing different records for the same zone:

view &quot;internal&quot; {
	match-clients { some-acl; };
	...
	zone &quot;example.com&quot; IN {
		type master;
		file &quot;internal/example.com.zone&quot;;
	};
};

view &quot;external&quot; {
	match-clients { other-acl; };
	...
	zone &quot;example.com&quot; IN {
		type master;
		file &quot;external/example.com.zone&quot;;
	};
};

Then, the contents of /var/named/internal/example.com.zone will be used when 
internal hosts query, and the contents of 
/var/named/external/example.com.zone will be used when external hosts 
query....

later,
chris


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00816" href="msg00816.html">[ale] DNS Questions</a></strong>
<ul><li><em>From:</em> kevinostoll at yahoo.com (Kevin O'Neill Stoll)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00818.html">[ale] Image programs for Linux?</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00820.html">[ale] Hoping someone can offer some advice</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00816.html">[ale] DNS Questions</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00802.html">[ale] O'Reilley book reviews</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00819"><strong>Date</strong></a></li>
<li><a href="threads.html#00819"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>