> > Dnscache+tinydns can be configured to do exactly what you > > describe. Bind > > dnscache to the internal interface of your LRP box and > > configure your > > internal hosts to use it as their DNS server. Bind tinydns > > to localhost > > (127.0.0.1) on the LRP box and load it with information on your > > 10.1.2.0/24 network. Tell dnscache to query 127.0.0.1 when > > it needs to > > resolve hosts on your local network. > > > > -Richard > > > That sounds promising. One questions, though. The tinydns sitting > on the Lrp localhost, 127.0.0.1, is not visible to the public because > it's not bound to the external nic, correct? And so the tinydns won't > need to be configured for external namespace, and Wacbell never needs > to know, either, am I right? > > Thanks, > Matt > Correct on all counts. In fact tinydns won't be visible to your internal network either. A request for dns service from an internal host goes to dnscache, which forwards queries about external networks to external servers, while passing requests for information about your internal network to tinydns; tinydns returns the requested information to dnscache, which passes it on to the internal host that made the original request.
-Richard _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
