[rbldnsd] RFC: wildcard entries in rbldnsd's dnset proposed change

[Michael Tokarev]

For the upcoming 0.98 release of rbldnsd, I made the
following incompatible change in dnset, and asking for
comments.  If no comments (or no objections) will be
made, I'll include this change into 0.98.

 From the news file:

  - feature, and incompatibility change in dnset DN interpretation.
    *.example.com is now NOT the same as .example.com.  Specify
    *.example.com to include all subdomains of example.com, and
    specify .example.com to include all subdomains AND example.com
    itself - instead of specifying 2 lines, only one is now needed.
    Looking for better variant to handle the same.. maybe *example.com?
    (but this is confusing - will it match noexample.com?)

 From the manpage:

        dnset  Set of  (possible  wildcarded)  domain  names  with
               associated  A  and  TXT values.  Similar to ip4set,
               but instead  of  IP  addresses,  data  consists  of
               domain  names  (not  in  reverse form).  One domain
               name per  line,  possible  starting  with  wildcard
               (either  with  star-dot (*.) or just a dot).  Entry
               starting  with  exclamation  sign   is   exclusion.
               Default value for all subsequent lines may be spec-
               ified by a line starting with a colon.

               Wildcards are interpreted as follows:

               example.com
                      only example.com domain is listed, not  sub-
                      domains thereof.  Not a wildcard entry.

               *.example.com
                      all  subdomains  of  example.com are listed,
                      but not example.com itself.

               .example.com
                      all  subdomains  of  example.com  and  exam-
                      ple.com itself are listed.  This is a short-
                      cut: to list a domain name  itself  and  all
                      it's  subdomains, one may either specify two
                      lines (example.com  and  *.example.com),  or
                      one line (.example.com).

Since the change is incompatible (i.e., currently existing
installations may break), I'm asking whenever this is ok or
not to do so..   Previously, *.example.com and .example.com
where treated equally.

/mjt