[rbldnsd] [PATCH] maxttl option

Michael Tokarev mjt at tls.msk.ru
Mon Mar 1 22:59:14 MSK 2004


Bradley Baetz wrote:
> We are running rbldnsd as nameserver, which bind speaks to via a forward
> zone.
> 
> So that bind doesn't cache these entries (which are being updated
> regularly via rsync), I've patched rbldnsd to have a maxttl option, so
> that bind will regularly requery rbldbsd.

I've implemented this feature, but slightly differently.

 From NEWS file:

  - feature: extended -t option, allow minttl and maxttl
    to be specified (to set constraints for TTLs found
    in data files).  New syntax is -t defttl:minttl:maxttl,
    with everything optional (so -t defttl works too, as
    well as -t ::1d).

 From the manpage:

  -t defttl:minttl:maxttl
    Set default reply time-to-live (TTL) value to be defttl, and set
    constraints  for TTL to minttl and maxttl.  Default applies when
    there's no TTL defined in a given  scope  (in  data  file),  and
    constraints  are  applied when such value provided in data.  Any
    of the values may be omitted, including trailing colon (:) char-
    acters,  e.g.  "-t 30"  set  default  TTL  to be 30 secound, and
    "-t ::120" or "-t ::2m" sets maximum allowed TTL to  2  minutes.
    All  3  values  are in time units, with optional suffix: s (sec-
    ounds, default), m (minutes), h (hours), d (days) or w  (weeks).
    Zero  minttl or maxttl means no corresponding constraint will be
    enforced.  Default defttl is 35m.

Hope this will be sufficient for now... ;)

/mjt


More information about the rbldnsd mailing list