JdeBP> I don't know whence you obtained that 96% figure from, but
JdeBP> the only survey done in recent years whose results I've seen
JdeBP> actually published puts BIND 4, 8, and 9 combined at 75% (of
JdeBP> the servers that actually responded), with "djbdns" at 8.5%,
JdeBP> eNom DNS server at 3%, with the remainder being either
JdeBP> unidentifiable or softwares with a 1% or less share.
JdeBP> <URL:
http://cr.yp.to/surveys/dns1.html>
NC> ok...if the 96% figure is the only major nit from my post...
NC> then I am a happy camper. ;-) 86% is ok too...
86% is _another_ figure that you appear to have come up with out of thin air.
The number for BIND that I gave was, as can be seen, 75%. Whence are you
obtaining these numbers from ?
NC> I was going a bit from memory...and consdering mostly the
NC> gTLD and ccTLD along with the legacy ROOT's.
That's both a far smaller sample than the one used by the actual survey, and a
biased one to boot. The survey surveyed just over two million domains,
whereas there are only just over a couple of hundred CCTLDs and GTLDs in the
diminutive root, a difference of several orders of magnitude (and a sample
size that is probably unacceptably small). And ICANN's "." content DNS
servers are strongly biased towards BIND, given that several of them (all of
the servers at 192.5.5.241 and at 2001:500::1035) are run by the very company
that writes BIND.
I haven't surveyed the CCTLD content DNS servers, or seen the results of
anyone else having done so (so, again, don't know whence you are obtaining
these figures, that you remember, from). I happen to know that one CCTLD just
recently switched from using BIND to using "djbdns".
NC> I don't consider MS DNS to be totally divorced in it's
NC> "heritage", [...]
It may use the same all-of-the-hats-at-once design, but it isn't derived from
BIND.
NC> eNOM may have never code (i haven't had chance to
NC> look) but the the original BIND writer is at eNOM now (iirc).
That sentence makes no sense.