Issues not essential to make the branch stable:

* Ignore leading or trailing whitespace in an ip_alias or ip_acl label

* Make the port number range that we bind to customizable

* Solaris support (DONE)

* Having the maximum number of TCP connections be allowed to be different
  value than the maximum number of threads running

* Not spawning a thread until after we determine the answer is _not_ in
  the recursive cache (and maybe not running the custodian unless we need
  to add answers to the cache).

"Wouldn't that be nice" issues (potential 1.2 material):

* Ability to disable case-insensitivity for queries sent to the
  recursor.

* We may (or may not) need a way of checking to make sure two different
  threads do not bind to the same port at the same time

* Make the cache size user-configurable (DONE)

* Round robin rotates of data in the cache (This is 1.2 material)

* Customizable root name servers which allow people to use different
  alternate registries for differnet TLDs.

* The ability to pritorize name servers.  Servers which do not respond to 
  queries at put at the bottom of such a list, minimizing the slowdown 
  caused by unresponsive servers.

* Signal handling (sighup, etc.)

* TCP name resolution (TCP: It's not just for zone transfers anymore)

Possible long-term issues:

* SQL support (Important--I have gotten three requests for this)

* The ability to have different ips which query the DNS server get different
  responses.

* ipv6 support (but not for A6 records.  See 
  http://cr.yp.to/djbdns/killa6.html)

* Support for wildcard records in the middle or the end of the domain label,
  e.g:

   mail.*.example.com
   somename.*

 (The first one might break the spec.  The second one *definitely* breaks the 
  spec.  C.F. RFC1034 4.3.3)

 I think the person who requested this is *really* after the ability to add
 domains without having to change any MaraDNS condiguration files.

