[rbldnsd] re-enabling a $TIMESTAMP-expired zone without restart?

[Anders Henke]

Hi,

while experimenting with $TIMESTAMP expires, I've found something
between a sideeffect or a major issue:

---cut
$TIMESTAMP 2006:07:06:13:11:16 +5m
127.0.0.2
---cut

I'm using Linux and chroot rbldnsd to /var/lib/rbldnsd/dist, so it
hasn't access to /etc/localtime and cannot accordingly use "local"
timestamps, it has to rely on UTC ones. rbldnsd checks for file updates
once a minute (default settings).

The current date is

UTC: Thu Jul  6 13:16:03 UTC 2006

and so the zone hasn't expired yet. A minute later, the zone expires:

Jul  6 15:16:21 rbldnsd1 rbldnsd[4488]: zone schlund.test: zone data expired, zone will not be serviced

However, if I change the timestamp or relative expire timeframe in the
file to a newer date or even +24h, rbldnsd reloads the file, but still 
complains that the zone data were expired. Manual reloads by means of
SIGHUP also show the same effects.

But if I'm restarting rbldnsd instead of only reloading it, it successfully
loads the unchanged "expired" zone and (correctly) serves it.

>From my point of view, rbldnsd should've reloaded the zone, noticed the new 
timestamp/expire data and start serving the new zone as long as the
current time is in the window between creation time and expire time.

Did anyone notice similar effects?


Anders
-- 
Schlund + Partner AG              Enlightenment und Systemadministration
Brauerstrasse 48                  v://49.721.91374.50
D-76135 Karlsruhe                 f://49.721.91374.225