From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] DNS [off-topic]
Date: Fri, 22 Mar 2002 14:26:56 +0000 [thread overview]
Message-ID: <marc-lartc-101680729729489@msgid-missing> (raw)
On Fri, Mar 22, 2002 at 09:16:51PM +0700, JefferySamuel@binus.ac.id wrote:
>
> is djbdns powerful enough to handle more than 500 domains ? many people
If you read up at the cr.yp.to/djbdns.html page, you'll find that some
people are using it for _thousands_ of domains. It is very powerful; it
uses disk caching to cache responses however, so frequently changing the
domain file will decrease performance somewhat; although write-through
caching should get you the same benefits if your OS has it.
> told me that djbdns is more secure than Bind, is it true ? I've installed
It is highly secure (no security bugs yet that I'm aware of; there's a
cash reward if you find any though). It is well-written from what I've read
of its source although variable naming is quite obscure but being written
by a mathematician probably explains that.
> djbdns on my development server but don't have courage to install it on my
> production server, my consideration is the stability, reliability and
> security...
It has never crashed for me.
It has never failed to respond for me.
It is my production DNS server (feel free to hammer away at fibrespeed.net
DNS requests if you like) ;-).
It has great local diagnostic tools and logging for any user-caused errors.
--
Michael T. Babcock
CTO, FibreSpeed Ltd. (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-03-22 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-101680729729489@msgid-missing \
--to=mbabcock@fibrespeed.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.