This is legacy DRBL generation utility. Prior versions (up to 1.04) were created by Kirill Vechera. Version 1.05 was released 25 Jan 2001 by D Kelmi aka MiksIr (miksir_AT_mixup.org.ru) and Vladimir B. Grebenschikov (vova_AT_express.ru). The program is written in Perl, so you shouldn't have any portability problem.
As of Jul 28, 2001, the version 1.06 has been published (the author is Dmitry Morozovsky (dmark_at_rinet.ru).
Here you can download the setup package for DRBL:Download drbl.tgz and extract its contents in some directory - e.g. /usr/local/drbl
Edit file zones - each line in this file consists of three fields: zone name, assigned zone weight, and the name of DNS where this zone is available via AXFR. For example:
vote.drbl.this.is.my.network.ru 1 ns.in.my.network.ru vote.drbl.piter.net 0.7 main.piter.net vote.drbl.tomsknet.ru 0.7 ns.tomsknet.ru vote.rsbs.express.ru 0.7 ns1.express.ru
Edit file header - it really is a header for generated .zone file and it should contain a valid SOA record for your WORK zone (hint: you can use $time$ macro as serial number - it will be replaced with value of time_t) and NS records. For example:
@ IN SOA ns1.mynetwork.ru. abuse.mynetwork.ru. (
$time$ ; Serial == sec. since epoch
10800 ; Refresh
1800 ; Retry
604800 ; Expire
86400 ) ; Minimum
IN NS ns1.mynetwork.ru.
IN NS ns2.mynetwork.ru.
Run build_drbl to generate WORK zone. Three necessary parameters are the full path to zones file, the threshold value, and the full path to header file. For example, if all files are in /usr/local/drbl/ directory, you might want to type:
cd /usr/local/drbl ./build_drbl ./zones 1 ./headerThe script will output generated zone to stdout. Check it, and if it is ok, repeat the previous command with output redirected to zone description file:
./build_drbl ./zones 1 ./header > /var/named/master/work.drbl.mynetwork.ru.zoneNow you have to reload named database for changes to take effect.
Once you became familiar with this procedure, you may add this to your crontab to be refreshed every N hours.
Fixed: Since this version the weight of an address is incremented by the weight of network it is in, only if it was not still incremented from this zone. For example: if address 4.3.2.1 came from vote1, and network *.3.2.1 came from vote2, then address 4.3.2.1 gains the weight of tho zones, but if both 4.3.2.1 and *.3.2.1 are received from zone vote3, then the weight of 4.3.2.1 is incremented only once.
Added (everything of these can be turned off):
(Comment from D Kelmi (MiksIr) miksir_AT_mixup.org.ru)
(c) Andrey V. Stolyarov (crocodil_AT_croco.net) 2000-2002
Portions (c) English version by Alexey V. Vissarionov (gremlin_AT_traktir.ru)
Last updates: December 06, 2002.