<html><head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"></head><body
bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
using bind 9.8.1-p1 on rhel5 i386<br>
<br>
Having a problem with views. My intended configuration:<br>
<br>
* most zones are identical in either view<br>
<br>
* a few zones are added in the internal view<br>
<br>
* networks in the internal view can do recursive queries (yeah, i know,
i'm not supposed to mix authoritative & recursing servers, but it's
not illegal, right?)<br>
<br>
I've configured things this way, and it basically works. <br>
<br>
<span>However, when I update a zone on my master server, the changes
are not
fully propagated to the slaves. The "internal" view on the slaves
generally picks up the changes; the "external" view, however, often
doesn't. <br>
<br>
I haven't been able to divine a pattern to when this happens and when it
doesn't. <br>
<br>
</span><span><span>I use rndc reload on the master to have
it pick up the changes.</span> </span><br>
<span>
</span><br>
Here are the view configs. the included files contain zone statements.<br>
<br>
As I write this, i wonder if the problem is because i include the same
authoritativezones.conf<span> file in all three views. <br>
<br>
========= begin<br>
</span><br>
<br>
view "internet2"<br>
{<br>
match-clients { some clients here };<br>
<br>
recursion yes;<br>
// you'd think "recursion yes" would enable recursion, but you'd
be wrong.<br>
allow-query-cache { any; };<br>
<br>
// all views must contain the root hints zone:<br>
include "stdzones/named.root.hints";<br>
<br>
include "conf/runtime/internet2.edu.conf";<br>
include "conf/runtime/authoritativezones.conf";<br>
};<br>
<br>
view "member-meetings"<br>
{<br>
match-clients { some other clients here };<br>
<br>
recursion yes;<br>
// you'd think "recursion yes" would enable recursion, but you'd
be wrong.<br>
allow-query-cache { any; };<br>
<br>
<br>
// all views must contain the root hints zone:<br>
include "stdzones/named.root.hints";<br>
<br>
include "conf/runtime/authoritativezones.conf";<br>
};<br>
<br>
view "external"<br>
{<br>
// This view will contain zones you want to serve only to "external"
clients<br>
// that have addresses that are not on your directly attached LAN
interface subnets:<br>
//<br>
match-clients { any; };<br>
match-destinations { any; };<br>
<br>
// you'd probably want to deny recursion to external clients, so
you don't<br>
// end up providing free DNS service to all takers<br>
recursion no;<br>
<br>
// Disable lookups for any cached data and root hints<br>
allow-query-cache { none ; };<br>
<br>
// all views must contain the root hints zone:<br>
include "stdzones/named.root.hints";<br>
<br>
// this should be a symlink, depending on master-slave status<br>
include "conf/runtime/authoritativezones.conf";<br>
<br>
};<br>
<br>
=========== end<br>
<br>
<br>
<br>
<br>
thanks!<br>
<br>
danno<br>
-- <br>
<div class="moz-signature"><span><pre wrap="">Dan Pritts, Sr. Systems Engineer
Internet2
office: +1-<span __postbox-detected-content="__postbox-detected-phone" class="__postbox-detected-content __postbox-detected-phone" style="display: inline; font-size: inherit; padding: 0pt;">734-352-4953</span> | mobile: +1-<span __postbox-detected-content="__postbox-detected-phone" class="__postbox-detected-content __postbox-detected-phone" style="display: inline; font-size: inherit; padding: 0pt;">734-834-7224</span></pre></span></div>
</body>
</html>