> Personally, I look forward to the day when djbdns runs on all the root servers.
Kingzongo, this will never happen. You might as well look forward to the flying spaghetti monster winning the 100m at the Olympics next year.
djbdns is a steaming pile of shit. If djbdns was anywhere near as good as its clueless fanbois claim, it would have been deployed for important zones like the root or a major TLD. None of these things use it. Which speaks volumes. In fact nobody who truly understands the DNS protocol or operations uses djbdns for anything significant. Aside from the long list of fundamental flaws in djbdns, it's almost impossible to make it play nice with other DNS implementations so that a zone can have more than code base for its DNS servers.
Many of the things needed for the root zone or a major TLD today, like Secure DNS, IDN, IPv6, EDNS0, TCP queries, IXFR, TSIG, etc are not implemented in djbdns AT ALL. Some of these might be do-able in djbdns by applying unsupported, informal patches and hoping for the best. Which is no way to run important internet infrastructure.
djbdns has not supported any DNS protocol work that's been done in the last 10-15 years. wikipedia says djbdns has effectively been abandonware since 1991. So what was it you were saying about the 1990s calling?
BIND9 (another pile of shit but not as smelly as djbdns) is a complete rewrite that was done in 2000 or theresabouts. It shares no code or software design with BIND4 or BIND8 which started in the 1980s. The same can't be said for most of the other long standing pillars of open source which will still contain code that was written well over a decade ago: emacs, x windows, BSD and Linux kernels, sendmail, apache, gcc, postfix, tex, mysql, perl, etc.