On Thu, 15 Mar 2007 00:18:18 +0000 (UTC)
Sam Trenholme <sam+djbdns@chaosring.org> wrote:
> That said, djbdns has a number of issues which make it not practical to
> deploy on new installations.
I certainly disagree with that.
> Djbdns has not changed one iota for over five years. In addition, it is
> not legal to distribute a changed version of djbdns. This is the number
> one problem with djbdns: Djbdns is not open source. Its license is not
> compatible with one fundamental pillar of open source: The right to
> distribute modified versions of a program
Personally I don't really care as long as it gets the job done.
> This is a very practical problem: There are high profile internet sites
> that djbdns' recursive resolver simply can not resolve. In order to make
> djbdns' recursive resolver resolve these sites, after downloading djbdns,
> you need to find the patch that fixes the broken recursive resolver,
> apply the patch, and hope the patch doesn't break anything.
Really? Care to give an example because I have never experienced this.
> Once djbdns is installed, you will find some directories in the root of
> your filesystem that weren't there before. This breaks UNIX and Linux
> standards on how the filesystem can be organized.
Only if you use daemontools. This is not a "problem" if you use runit,for
example.
I also question wether this is actually a problem.
> Djbdns was the best DNS option available when it came out. That was
> over five years ago. Since then, the internet has changed and djbdns has
> not kept up.
It still is the best for my needs.
--
Lars Hansson <lars@unet.net.ph>
|