No subject

An honest question, as I'll admit I haven't wasted my time trying to
figure out your arcane packaging with its myriad dependencies and
configuration gunk (I find it much easier to type ./configure;make and
have a self-contained binary).  Does tinydns (or dnscache or pickdns or
whatever) support:

- DNS-over-TCP by default?
- full (incoming and outgoing) AXFR?
- IXFR?
- NXT?
- SIG?
- KEY?
- TSIG?
- Notify?
- Dynamic Update?
- A6?
- DNAME?
- bitstring labels?

By the way, how does an administrator of a site with NT boxes, 390
boxes, AS/400 boxes, or any box which doesn't support rsynch+openssh do
zone transfers with your stuff?

As an aside, someday I'll have to take the time to figure out all the
dependencies and requirements and benchmark your stuff.  You claim
reports of 500 queries per second on a PIII-550.  A PIII-450 running
stock BIND (v8.2.2p5) was happily responding to 2500 queries per second
sustained, about 5000 queries per second peak.

> In fact, I've been extremely
> careful to make sure that djbdns works correctly. 

For _your_ definition of "correctly".  It would seem (typically,
according to the many people who have dealt with you in the past and who
have sent me private email since you showed up here) that you can't be
bothered to implement the parts of specifications you don't agree with,
regardless of the impact on interoperability.

> It's funny how the BIND company keeps talking about standards compliance
> when BIND can't even get the basics right.

Uh, right.  Basics like zone transfers, right Dan?

I'll be more than happy to put BINDv9 (the first version of BIND written
by us (which is who I assume "the BIND company" is supposed to mean)) up
against any of your myriad programs for verification of standards
compliance by a neutral third party (if one can be found -- you have a
tendency to not make friends) any time you like.

Any time, Dan.

Rgds,
-drc