On Tue, 2002-12-24 at 10:35, Gary wrote: > Yah, it's terrific isn't it. >
Oh yes, it's real nice. :) I have a guaranteed DNS server and don't have to worry about remote DNS crashes or anything like that. :) > > One thing that confuses me though, is whether tinydns uses the same cache that >dnscache uses. Do I have to use dnscache along with tinydns? > > No, no ... tinydns does not cache anything. It is a content server, > publishing DNS content to the world.. Dnscache is a caching proxy server, > never listing deligations like tinydns, and can be used either as a > forwarding or resolving proxy server, depending on your needs. They are > separate programs, and not like BIND which has both together... In fact, > dnscache and tinydns run on separate IP addresses within a single > computer. I do this by aliasing tinydns another 192.168.x.x. address off > of eth0. Using dnscache alone, for one machine, workstation, can just run > on 127.0.0.x. I see! I am going to implement tinyDNS on a Linux server in lieu of BIND. I just didn't know if it cached anything itself. Only problem is that there aren't any web based tools to update info for tinydns, after hunting around for some. I'm still leaning towards tinydns for the speed, and if it doesn't cache, no problem, I don't think that'll be necessary. :) > you do not have to use both together, and many people just use dnscache, > even on one workstation, just to speed up their web experience. > > For an in-depth understanding of the difference, please see > > http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-server-roles.html#Content > > and for an overall big picture of djbdns, > > http://homepages.tesco.net./~J.deBoynePollard/FGA/djbdns-big-picture.html Thanks! :-D I'll definitely give these a read before implementing tinyDNS. -- Brian Wright <[EMAIL PROTECTED]> Aturn Communications -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
