-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Theo Van Dinter writes: > On Mon, Dec 19, 2005 at 07:07:32PM -0800, Justin Mason wrote: > > each time an update tarball is created, the zone serial number for the > > "top level" spamassassin.org SOA needs to be incremented. > > > > I'd prefer to avoid this, but I can't really see a way to do so, unless we > > explicitly set up updates.spamassassin.org. as a separate zone with a > > separate SOA of its own -- and therefore separate secondaries etc! > > Yeah, I had been going back and forth thinking about this issue. I generally > decided that keeping the single zone will make things easier. If the updates > traffic gets to be too much, we could split it off, but I doubt that'll happen > anytime soon. I was more worried about the danger aspects of auto-editing the zone file daily ;) The records for updates can be done with a $INCLUDE, but I'm not sure about the SOA line. > It's not really a big deal to update the main zone instead of just the updates > area. We can easily do 100 revisions per day while keeping the YYYYMMDDVV > format, and the current servers will probably do IXFR to transfer diffs > around. OK; if you're not too worried, I'm not either ;) - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Exmh CVS iD8DBQFDp3/sMJF5cimLx9ARAnnpAJ4hiayjLqu9E+vmH9a9bi/q0W+7XwCcD/H8 FhNlpS35pxvcki/2DvQo2XQ= =Rpcm -----END PGP SIGNATURE-----
