Date: Mon, 2 Apr 2001 21:34:30 +0200 From: "Clemens Hermann" <haribeau@gmx.de> To: "Sean Chittenden" <sean-freebsd-isp@chittenden.org>, "John Brooks" <john@day-light.com> Cc: <freebsd-isp@freebsd.org> Subject: Re: djbdns or tinydns Message-ID: <009601c0bbab$f0e0f410$fe78a8c0@espe.de> References: <5.0.0.25.0.20010228000158.0436aeb0@mail.Go2France.com> <000201c0bb1a$8eacb180$0b00a8c0@dle> <20010401200432.A26747@rand.tgd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Sean and John, > I've had extremely favorable experiences with djbdns. same with me. - Simple setup - clean structure - rock-solid - ressource-friendly > 1) You will need _at least_ one more IP address (recursive dns server > and authoritative dns server are different daemons: good thing). but you can use (e.g.) the loopback device for the recursive resolver. This way you have a reliable (!) resolver for your server which will improve security a lot in many cases. Furthermore you are not misused as publicly available resolver in case you only want to provide authorative dns for your domains. > 3) The data files are extremely easy to view, scan, and update via > hand and from scripts/databases. ACK furthermore djbdns can perfectly coexist with bind (use bind as secondary or be socondary for a bind server) I have used Bind for a while. After I switched to djbdns I begun to understand DNS ;-) bye /ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?009601c0bbab$f0e0f410$fe78a8c0>