The mDnsResponder project is still alpha code and is missing some necessary
features and functionality before moving to what I would consider
Beta quality.

The mDnsResponder needs configuration
information for controlling the logging output.  BTW, mDnsResponder uses
log4net for all logging.  Local static DNS records could also be configured
in the XML configuration file and passed to mDnsResponder through the
registration API.

Currently the mDnsResponder does not multi-cast query its local host address
record before adding itself to the resource list.  Also it does not defend its
local host address record when another responder is attempting to use the same
name.  Both these features need to be implemented soon.

The mDnsResponder does not multi-cast "dying" packets when resource records
are removed from the system or when the daemon itself is taken down.

The mDnsResponder does not support "Answer Suppression" for query packets. 
If a client issues a query with a Question and also tacks on known answers in
the query the responder will blindly return answers the caller knows about.
This needs to be fixed ASAP.

The mDnsResponder does not support packet compression when returning a list
of answers with equivalent domain name components.  This does not need to be
implemented any time soon.

The command line client mDnsResponderCmd is not finished and does not expose
all the needed functionality of the responder.  It's barely past prototype
stage.

If you have any other questions you may contact me directly.

Brady Anderson
801-861-3130
banderso@novell.com
