David Nicol wrote: > On 6/30/05, John Peacock <[EMAIL PROTECTED]> wrote: > >>Elliot F wrote: >> >>>Another method (and a very scalable one) would be to store user data in DNS. >> >>Ooh, don't suggest that sort of thing on a DNS admin list unless you really >>like >>having a cheese grater rubbed on all your private parts. That is a gross >>violation of the design of DNS (but of course I can think of an elegant way to >>do it with a tinydns instance ;-). > > > PowerDNS appears to be proud that it uses a database for a DNS server > backend. If > that doesn't invite publishing user data by DNS I'll be plunged into > syrup and called > a hotcake. I am not aware of a standard LDAP->DNS translation mechanism, but > I would not be surprised if several exist.
I was intrigued by PowerDNS, but prefer the cleanliness that an exporter to tinydns allows. It isn't as flexible, but (in my mind) a bit more trustworthy. It would be easy to use the schema that PowerDNS uses, though. There are a few schemas that are available, if I recall correctly, but if you used the schema from PowerDNS, you could use the frontend that PowerDNS uses for domain management (though it wouldn't be hard to whip one up.) One could also use ldapdns, ldap2dns, mydns, etc... There are more mature implementations of the idea. Anyway, it was another idea, on topic while John was talking about methods of validating user addresses.
