Karsten Bräckelmann wrote: > On Mon, 2010-02-01 at 22:33 +0100, Yet Another Ninja wrote: >> - If someone knows how to put these two rule sets in one file and >> "activate" according to SA version, pls let me know... I'm stumped. > > Preprocessing Options [1] in the SA Conf documentation. :) > > if (version >= 3.003000) > # util_rb_3tld blob goes here > endif > > Hmm, doesn't mention >= specifically. Guess it's supported, though, > otherwise you'd need a minor hack like > 3.002999.
Yes, please implement that within the same channel so as to limit the need for admins to edit their channel list files. The DNS entries for this channel lack version noting as well: $ host -t txt 0.0.2.90_2tld.cf.sare.sa-update.dostech.net 0.2.90_2tld.cf.sare.sa-update.dostech.net descriptive text "200912211500" So it's apparently okay to use that channel for SA version 2.0.0... This is easily solved by changing the wildcard entry in BIND (assuming you're using BIND), e.g. 4.2.3.90_2tld.cf.sare.sa-update IN TXT "200912211500" 5.2.3.90_2tld.cf.sare.sa-update IN TXT "200912211500" 6.2.3.90_2tld.cf.sare.sa-update IN TXT "200912211500" *.3.3.90_2tld.cf.sare.sa-update IN TXT "200912211500" *.4.3.90_2tld.cf.sare.sa-update IN TXT "200912211500" That should cover the future revisions 3.2.6 and 3.4.x in addition to the current (new) 3.3.x branch and the two valid previous releases of 3.2.4 and 3.2.5. (I don't think BIND supports other globs.) Surely this shouldn't be hard to add to your publish script... It also has the added advantage of preventing future use of a horribly stale channel e.g. when 3.5.0 comes out. Just write yourself a note that you'll need to update the publishing script or else suffer the complaints. ;-)
