One Domain; Multiple IPs.

Jim Reid jim at rfc1035.com
Tue Jul 17 09:37:22 UTC 2001


Your comparison table between djbdns and BIND is missing a few things,
like compliance with Internet standards and interoperability with the
installed base of other DNS implementations. Funny that: your list
utterly misses the fundamentals but is filled of things which are
pointless and irrelevant. And padded out with repetition too. For
instance rsync over SSH is all very well, but is completely useless
for platforms that don't have these things. [Have either rsync or SSH
even been ported to a mainframe?]  BTW, which RFC defines the rsync
protocol? As the DNS reference implementation, BIND has to comply with
all the DNS standards. Unlike djbdns which can opt-out from stuff
that's too hard to implement or that you don't like. And as you've
been told here often enough, if you think you can design and document
better protocols than AXFR and IXFR, you're more than welcome to
participate in the standardisation process and submit those proposals
to the IETF. How come you don't do that? And why have you consistently
failed to answer that question? Is it because you know that you'd need
to seriously address difficult problems such as the issue of
interoperability and not breaking anything for the current installed
base?


More information about the bind-users mailing list