<div dir="ltr"><span style="font-size:12.8px">I'm going to try slaves like so</span><div style="font-size:12.8px"><br></div><div style="font-size:12.8px"><div style="font-size:12.8px">If I setup slave zones like so on 192.168.1.1</div><div style="font-size:12.8px"><br></div><div><span style="font-size:12.8px">zone "</span><span style="font-size:12.8px">domainA</span><span style="font-size:12.8px">" IN { type slave; masters { 192.168.2.1; }; file "db.domainA"; };</span><br></div><div><span style="font-size:12.8px">zone "</span><span style="font-size:12.8px">domainB</span><span style="font-size:12.8px">" IN { type slave; masters { 192.168.3.1; }; file "db.domainB"; };</span><br></div><div><br></div><div><span style="font-size:12.8px">and in </span>192.168.2.1 and 192.168.3.1</div></div><div style="font-size:12.8px">in options</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">notify yes;<br></div><div style="font-size:12.8px"><div>also-notify { 192.168.1.1; };</div><div>allow-transfer { 192.168.1.1; };</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 27, 2016 at 1:20 PM, Jeff Sadowski <span dir="ltr"><<a href="mailto:jeff.sadowski@gmail.com" target="_blank">jeff.sadowski@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I'm going to try slaves like so<div><br></div><div><div style="font-size:12.8px">If I setup slave zones like so on 192.168.1.1</div><div style="font-size:12.8px"><br></div><div><span style="font-size:12.8px">zone "</span><span style="font-size:12.8px">domainA</span><span style="font-size:12.8px">" IN { type slave; masters { 192.168.2.1; }; file "db.domainA"; };</span><br></div><div><span style="font-size:12.8px">zone "</span><span style="font-size:12.8px">domainB</span><span style="font-size:12.8px">" IN { type slave; masters { 192.168.3.1; }; file "db.domainB"; };</span><br></div><div><br></div><div><span style="font-size:12.8px">and in </span>192.168.2.1 and 192.168.3.1</div></div><div>in options</div><div><br></div><div>notify yes;<br></div><div><div>also-notify { 192.168.1.252; };</div><div>allow-transfer { 192.168.1.252; };</div></div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 27, 2016 at 1:11 PM, <span dir="ltr"><<a href="mailto:wbrown@e1b.org" target="_blank">wbrown@e1b.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><tt><font size="2">> From: Jeff Sadowski <<a href="mailto:jeff.sadowski@gmail.com" target="_blank">jeff.sadowski@gmail.com</a>></font></tt>
<br><span>
<br><tt><font size="2">> On the samba mailing list they described setting
up the DC as the NS<br>
> and forward to another machine for more rules.</font></tt>
<br><tt><font size="2">> This will work fine for one domain. Now lets
say I have 2 domains.</font></tt>
<br><tt><font size="2">> <br>
> If I setup forwarders like so on 192.168.1.1</font></tt>
<br><tt><font size="2">> <br>
> zone "domainA" IN { type forward; forward only; forwarders
{ 192.<br>
> 168.2.1; }; };</font></tt>
<br><tt><font size="2">> zone "domainB" IN { type forward; forward
only; forwarders { 192.<br>
> 168.3.1; }; };</font></tt>
<br><tt><font size="2">> <br>
> It will cache entries for each domain and if a computer gets a <br>
> different address for dhcp it will update on the domain's DNS but
<br>
> the dns on 192.168.1.1 will have a cached entry untill it expires.</font></tt>
<br><tt><font size="2">> <br>
> 192.168.2.1 and 192.168.3.1 are setup to forward all other zones <br>
> than their domain names to 192.168.1.1</font></tt>
<br>
<br></span><tt><font size="2">Your Domain Controllers should be the DNS servers
for any computer in that domain. Forward any other queries to a recursive
server (192.169.1.1?) which may or may not be authoritative for other domains.</font></tt>
<br><span><tt><font size="2"> </font></tt>
<br><tt><font size="2">> if I have DNS server set for all machines in
domainA to 192.168.2.1 <br>
> all machines on domainA see any DNS changes to domainA imediately
<br>
> machines on domainB are cached and can take time to clear out.</font></tt>
<br><tt><font size="2">> And</font></tt>
<br><tt><font size="2">> if I have DNS server set for all machines in
domainB to 192.168.3.1 <br>
> all machines on domainB see any DNS changes to domainB imediately
<br>
> machines on domainA are cached and can take time to clear out.</font></tt>
<br>
<br></span><tt><font size="2"> Yep, thats how it works.</font></tt>
<br><span><tt><font size="2"><br>
> What is the best way to resolve this issue?</font></tt>
<br>
<br></span><tt><font size="2">Short TTLs in your domain controller DNS. </font></tt><font size="1" face="Arial"><i><br>
<br>
</i></font>
<hr><font size="1" face="Arial"><i><br>
Confidentiality Notice: <br>
This electronic message and any attachments may contain confidential or
privileged information, and is intended only for the individual or entity
identified above as the addressee. If you are not the addressee (or the
employee or agent responsible to deliver it to the addressee), or if this
message has been addressed to you in error, you are hereby notified that
you may not copy, forward, disclose or use any part of this message or
any attachments. Please notify the sender immediately by return e-mail
or telephone and delete this message from your system.</i></font><font size="2" face="sans-serif"><br>
</font></blockquote></div><br></div>
</div></div></blockquote></div><br></div>