<html><head></head><body><div class="ydp1a52dd7dyahoo-style-wrap" style="font-family:Arial, Helvetica, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">Just to clarify, the configuration I was referring to was supposed to have a master and slave DNS server for private zones (only two DNS servers) but something happened during/after upgrade and they both showed master (actually rndc -s 127.0.0.1 <span>-r zonestatus <zone - both forward and reverse for all zones>) </span>reported master and the other primary.</div><div><br></div>
</div><div id="ydpff9d86ayahoo_quoted_4718147542" class="ydpff9d86ayahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Thursday, September 7, 2023 at 04:09:04 PM CDT, Fred Morris <m3047@m3047.net> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Hi Greg.<br clear="none"><br clear="none">So somebody referenced this KB article because presumably it was <br clear="none">tangentially relevant, but I don't know that the OP is working with <br clear="none">standby infrastructure (good question!). All they say is that after an <br clear="none">upgrade all servers were masters.<br clear="none"><br clear="none">The amount of direct relevance of the article is questionable. <br clear="none">Nonetheless, paragraph two seems factually incorrect on its face: changing <br clear="none">type master; to type slave; does not swich a server from secondary to <br clear="none">master, last I checked it did the opposite.<br clear="none"><br clear="none">On Thu, 7 Sep 2023, Greg Choules wrote:<br clear="none">> <br clear="none">> Hi Fred.<br clear="none">> No, the sense is correct.<br clear="none">> Imagine you have a server with a secondary zone of (say) "example.com",<br clear="none">> which transfers data for that zone from a primary somewhere.<br clear="none"><br clear="none">The KB article talks about multiple masters. At the outset there is no <br clear="none">secondary.<br clear="none"><br clear="none">> The secondary<br clear="none">> loads data received during a zone transfer straight into memory and uses it.<br clear="none">> It is optional for the secondary to also write that data to a file on its<br clear="none">> local storage, if you specify a "file" statement in the zone declaration.<br clear="none"><br clear="none">All examples (barring questions of relevance) of configuration syntax in <br clear="none">the article specify a file statement. In one case it's implicit as in <br clear="none">masterfile-format raw; and in the other it's quite explicit (but both of <br clear="none">the examples are talking about standby primaries, which are not an <br clear="none">explicit thing in the software although they are conceptually understood).<br clear="none"><br clear="none">Please re-read the second paragraph and try again.<br clear="none"><br clear="none">> If the server currently being secondary for "example.com" does write that<br clear="none">> zone to disc then it is easy to switch it to become primary because it<br clear="none">> already has the zone file stored locally. Just change the "type", leave the<br clear="none">> "file" statement alone and delete (or comment) the "primaries".<br clear="none"><br clear="none">Agreed.<br clear="none"><br clear="none">> Does that help?<br clear="none"><br clear="none">No. I have personally set up and administered a corosync / pacemaker <br clear="none">cluster to do a standby to master promotion (for publishing RPZs with <br clear="none">BIND) in a past life.<br clear="none"><br clear="none">Respectfully...<div class="ydpff9d86ayqt6363382591" id="ydpff9d86ayqtfd02272"><br clear="none"><br clear="none">--<br clear="none"><br clear="none">Fred<br clear="none">-- <br clear="none">Visit <a shape="rect" href="https://lists.isc.org/mailman/listinfo/bind-users" rel="nofollow" target="_blank">https://lists.isc.org/mailman/listinfo/bind-users</a> to unsubscribe from this list<br clear="none"><br clear="none">ISC funds the development of this software with paid support subscriptions. Contact us at <a shape="rect" href="https://www.isc.org/contact/" rel="nofollow" target="_blank">https://www.isc.org/contact/</a> for more information.<br clear="none"><br clear="none"><br clear="none">bind-users mailing list<br clear="none"><a shape="rect" href="mailto:bind-users@lists.isc.org" rel="nofollow" target="_blank">bind-users@lists.isc.org</a><br clear="none"><a shape="rect" href="https://lists.isc.org/mailman/listinfo/bind-users" rel="nofollow" target="_blank">https://lists.isc.org/mailman/listinfo/bind-users</a><br clear="none"></div></div></div>
</div>
</div></body></html>