[EMAIL PROTECTED] wrote: > On Friday 24 September 2004 06:34 pm, Geoff Nordli wrote: >> My understanding is if you have specific domains that you would like >> resolved then you have to populate the /etc/dnscache/root/servers/ >> directory with the name of domains and the servers that are able to >> resolve those domains. Tinydns is resolving my domaina.com so I >> created the domaina.com file in the /etc/dnscache/root/servers and >> entered 127.0.0.1. So when dnscache gets a request for domaina.com >> it will pass that on to the server residing on 127.0.0.1. > > Ahhh.... a more complete picture now, is tinydns residing on > the same box? > dnscache cannon be authoritive, so you need dnscache to > refer to tinydns > for the private domain. First you CANNOT bind both tinydns > and dnscache > to the same address. As resolv.conf generally points to > localhost first, you > need to bind tinydns to 127.0.0.1. Then you bind dnscache to > the actual > interface (stock is 192.168.1.254) and have your private > clients use this > internal address as their DNS server. Setup this way, the > clients will poll > dnscache which will in turn poll tinydns. > > It appears that you are attempting to run dnscache > authoritive, which breaks > several RFC's and is NOT suggested. Bind the interfaces/address's as > noted above. Setup the services through the lrcfg menu, as > that is where > they are to be configured running DJB's daemontools instead of the > typical init.d scripts. > > Link to the Bering Users Manual concerning dnscache: > http://leaf.sourceforge.net/devel/jnilo/dnscache3.html#AEN96
I read through the jnilo's page about the dns and everything was configured OK. I installed the daemontl.lrp package as per the documentation. One of the nice things about Leaf/Bering is the great documentation, especially the shorewall configuration. BTW tinydns and dnscache binding to the same ports had me stumped for a couple of hours. Though it was so obvious after I figured it out. Maybe this is something that should be added to the documentation when downloading tinydns. I added the /etc/dnscache/root/servers/* to the dnscache.list file and did a backup. It looks like the files were backed up OK. I won't know for sure until I do a reboot next week. If this is the correct fix then it should also be added to the dnscache docs. Thanks for all your time. Have a great weekend. Geoff ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
