[rbldnsd] almost got it running but missing a few important lines somewhere

Michael Tokarev mjt at tls.msk.ru
Thu Sep 22 17:54:20 MSD 2005


Sebastiaan Tigchelaar wrote:
> Its working ^_^
> 
> 2 things that puzzle me:
> 
> All zonefiles start with
> $NS 120 create.my.own.rbl.
> $TTL 2d

Are you sure 2d isn't too large?

> Yet 2 files give the message "compatibility mode: specify all NS records
> in ONE line"

This comes due to two points.

The "DNS Meta-Data" is actually per-*zone*, not per-dataset (the term
"dataset" has no meaning for DNS whatsoever).  You specified 3 *zones*
(as in zone:dstype:dsfiles arguments in command line), but multiple
dataset files for each zone.  Rbldnsd constructs NS records (and other
DNS metadata) from all datasets (and dataset files), hence it sees
"$NS ..." lines multiple times in every dataset.  Hence it complains,
because currently, only one "$NS ..." line is allowed.  And yes it's
not smart enouth to recognize it's the same hostname at that stage.

Since you're using 3rd-party source files for your data, it may be
better/simpler to specify yet another datafile that only contains
your site-specific (meta-)data in it:

 zone.example.com:ip4set:metadata,africa,europe,whatever

where files "africa", "europe" etc comes from your sources, and
the file "metadata" only contain $NS and $TTL record(s) and contain
no real DNSBL-specific data (IP addresses/ranges/etc).

> Second thing I think you might have noticed already ~_^ every last line
> in the zonefiles are ignored for being incomplete.
> No matter what I place there, is this by design?
> I placed 255.255.255.0 to fill it up in the end.

Rbldnsd complains like that if there's no end-of-line
character (linefeed, ascii 10 (0x0a)) at the end of last
line.  *This* is by design, yes.  If last character in your
file(s) *is* the linefeed, please send me a sample (in a
tar.gz archive).

> Sebastiaan

/mjt


More information about the rbldnsd mailing list