bind vs djbdns

[D. J. Bernstein]

Ruben I Safir writes:
> But the fact that your DNS is cutting corners is real concern.

Perhaps it would be if it were true. In fact, I've been extremely
careful to make sure that djbdns works correctly. Some examples:

   * BIND versions 4.9.* through 8.1.2 compress RP records. This simply
     doesn't work; it breaks RP lookups by older versions and by other
     caches. (Be thankful that RP isn't used for anything important.)
     djbdns strictly follows the standard compression protocol.

   * When BIND sees a glueless delegation, it drops the original query.
     This bug, which the BIND company calls ``no query restart,'' delays
     and often loses responses even when every network and server is up.
     djbdns handles as many as three levels of gluelessness.

   * BIND has all sorts of problems handling record types that it
     doesn't recognize, such as all record types newer than the BIND
     installation. Zone transfers involving those types die horribly.
     djbdns can deal with any record type.

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

---Dan