Does anyone know of a good web hosting company that uses DBJDNS?



http://cr.yp.to/djbdns.html

I am sorry, I thought he was using djbdns, but he apparently is using TinyDNS these days.

studpenguin, Dan is a real loud-mouth, but he who screams loudest doesn't necessarily know the most. There are several areas where DJBDNS fails, one of which is the bizarre and restrictive license, another is that none of DJB's stuff supports IPv6, and he has been outspoken about not supporting IPv6. I would do a lot more research before convincing myself that DJB is a god and his DNS rules all.

Well Bernstein has clearly stated that he will ONLY IMPLEMENT THE THINGS HE LIKE - so this is about to break standards...

What standards are those?

It's his own freakin' software!!!!

studpenguin, if you are so stuck on using or learning about DJBDNS, then why don't you do a little searching first? I know you are buisy so I will help you:
http://www.google.com/linux?hl=en&lr...=Google+Search


Hope this helps

/boggle

You really don't know what you're talking about, do you? DNS standards. There is a DNS standard for IPv6, but he won't implement it. There are other things he doesn't do, either (check Qmail for some of the other examples) but IPv6 is the major one. Yes he writes the software and he can make it do whatever he wants, but it's software that implements standard services, and those services are expected to behave in certain ways and have certain features, a fact that DJB seems to conveniently ignore.

Like I wrote in the other thread, maybe we shouldn't be following the herd of "standards"

I had thought I wrote that IPv6 would involve

340,282,856,360,466,376,620,684,388,469,930,214,496 different numbers

IPv4 would only involve only 4,294,967,296 and could be further expanded to meet the needs of growing numbers of computers and servers with CIDR notation Classless addresses.


Why make the world more complicated than it already is?

Why is IPv6 a good thing? Well for starters, the real benefit of CIDR is route aggregation to shrink the global routing tables. IPv6 doesn't change that, despite having more IPs (you can just aggregate bigger blocks, no difference to the routing table as far as number of entries). Also, NAT is a fairly necessary hack in order to leave a comfortable amount of IPv4 addresses to assign. NAT has the rather unfortunate effect of making IPSec frustrating and some times impossible to implement. With IPv6, you can use a lot more "real" IPs rather than NAT'ing, which makes it much more IPSec-friendly. Oh, speaking of IPSec, it's built into IPv6 rather than an extension like it is for IPv4.

Just think if your broadband ISP could no longer give you the BS of needing to pay for extra static IPs. Everyone could have 5 or 10 static IPs on IPv6 and there would be no noticable impact.

Really, all this information can be found on Google and in many mailing list archives. I would suggest that you start reading other material besides just the rantings of DJB. Anyone looks like a genius when no one is around to refute their points. If you start reading what other people have written, you'll soon see that many people do not agree with DJB's point of view.

Dan Bernstein is a security nut. Now that isn't a bad thing. Qmail is wonderful though it does need a few patches in order to be up to todays MTA standards.

I use DJB's daemon tools and Qmail. And I love the way both of them work. I also think it is just fine for him to release the software the way he does, because after all, it is his software. But I also think that if/when IPv6 becomes the standard most people go by djbdns is going to do one of two things a) implement IPv6, or b) become fairly useless.

"I would suggest that you start reading other material besides just the rantings of DJB."

That's exactly why I'm asking questions here:

to read people's answers, to read other people's "material"

DnsCache and TinyDns are two of the packages (among others: daemontools) that MakeUp DJBDNS as a whole.

studpenguin you said:
I don't understand what your getting at here? Please explain.

Have you thought about joing the djbdns mailing list. If your serious about djbdns then I would seriously consider joing that list. I did and it helped tremendously. You'll get the best answers to your questions from very experienced friendly users.

Not to attract any Troll's but I think the djbdns package rocks. I use dnscache internally that all clients point too for dns lookups. I've set the cache to be at 4megs. I use tinydns internally to serve up internal namespace. So I can connect to anything by dnsname internally.... web, ftp, mail, ect. ect..

I don't have to depend on the ISP's dns servers and setting up the TinyDns content server was tooooo easy. Compaired to Bind that is. And I'm not a Bind basher. I just found Bind to be way to complicated.

Good luck...