[rbldnsd] Problems configuring BIND 9 with rbldnsd

[Benny Pedersen]

> Benny Pedersen wrote:
>> http://uribl.com/ using gzip compressed zone files to save mirror trafic
>> rbldnsd reads dhcp.gz compressed
>> so it will be bandwidth saver if the zones could be rsynced in gzip form aswell
> Heh.
> It's not that simple, really.

me is just laerning

> With "plain" gzip, rsync will be almost as good as http/ftp/whatever
> "plain" download mechanism you use (rsync being an "advanced" mechanism).
>
> Because even very small change in original data changes compressed stream
> *alot*, so rsync is just unable to find any unchanged pieces and hence
> acts just like plain (but very CPU-hungry) http.

-z, --compress              compress file data during the transfer
     --compress-level=NUM    explicitly set compression level

it can be set off

makes sense to me if one rsync a compressed file to disable this compressing in rsync

> There's a patch for gzip circulating around, that adds --rsyncable option,
> so resulting gzip data becomes a bit larger and a bit more rsync-friendly.
>
> But using rsync is useful in the first place only if the data is large and
> the changes are small, and even when, good ordering is very important (and it's not at all obvious what is
> "good ordering" in this case).

real life counts :)

most of the time i don't understand all options in the software i use, but in the end i get it working
optimal by checking what bad options do, yes and there is alot of good books, but the problem will be the
same as read  some man pages :=)

> Yes, compressed file d/loaded using http is a big win compared to
> uncompressed data over http.  But usage of rsync isn't this simple, and in many cases (simplistic) rsync
> approach is more costly than http.

so wget can some times be more bandwidth saver then rsync ?