| |||
| bsd | dude, where's my code? | ||
| code | hacking for the masses | ||
| contact | solo sex does not qualify as reaching out and touching someone | ||
| gnu | what it means to be free | ||
| history | what state of mental health? | ||
| microsoft | on the lack of innovation | ||
| mrt | get out of school, do drugs, don't drink milk | ||
| phil | an ode to my favorite groundhog | ||
| religion | i am write and you are wrong | ||
| schismtracker | what makes good software great | ||
| secure | tightrope walking without a net | ||
( home : code : ldapdns ... kchuid ) On the sixth day God created man On the seventh day, man returned the favor.
ldapdns.tgz ... DOWNLOAD ... 2.06 (newest) / 2.05 / 2.04 / 2.03 / 2.02 / 2.01 / 2.00-10 / 2.00-9 / 2.00-8 / 2.00-7 / 2.00-6 / 2.00-5 ... README ... CHANGELOG ... FAQ ...
ldapdns mailing list ... mailing list archives disabled temporarily....
binary packages for ldapdns ... i386 OpenBSD maintained by Giacomo Cariello ...i386 Fedora 3 maintained by Simon Matter ...i586 Mandrake 9.x maintained by Oden Eriksson ...
ATTENTION
LDAPDNS 3 will not be published here. eventually this page will disappear completely. LDAPDNS 3 is moving to sourceforge. the project name is ldapdns and you can get it using: http://ldapdns.sf.net
THE NAMESERVER
ldapdns is a fast and rhobust root-nameserver that can outperform bind and djbdns on medium to large installations, and will scale well both up and down.
the secret is that ldapdns uses a threaded core, and takes advantage of an external directory. it's extremely simple, and it does not run under user-control as root.
it's ideal for small and large installations, because it queries the ldap server directly, updates are immediate. you don't have to rebuild constant databases, or wait for bind to get it's shit in gear.
but ldapdns is a work-in-progress. i use it on a production network, as do many others. but it's up to you to make it best for your network.
THE LEGEND
i wrote ldapdns because i needed the ability to make instant updates. i also wanted to push my company into using LDAP. ldap2dns and the bind+ldap projects were both considered. they're both inadaquite.
many people have MADE them work, but i can code. so code i shall. i will not settle for second-rate software; nor something that only pretends to do what i want.
so i created ldapdns- originally using the djbdns core. the upshot was that the first version took a little under 2 hours to write.
SOME ADDITIONAL HUMOR
i'd like to think ldapdns and djbdns have something in common, not the least of which I've tried to borrow some concepts of djbdns: but for the most part, ldapdns doesn't have any dns-protocol related features that djbdns doesn't (yes, i know, i support several things djbdns doesn't- but djb is absolutely right: you don't need them to do dns).
Some people, who won't get linked to here, have quoted ldapdns as a preferable alternative to djbdns- despite the fact that the clearer points (separate programs for axfr and normal dns traffic, weird file structure, etc) where reasons for not using djbdns- which I happen to like and have emulated with ldapdns.
Some people also seem to confuse tinyldap with ldapdns. I often thought ldap2dns and ldapdns would get confused, but no: it's tinyldap. the record is straight: tinyldap is an LDAP server, while ldapdns is a DNS server. they're not the same thing, they're not by the same author, and about the only thing we have in common is the fact both projects were influenced by djb's code.
⠄⠵