> How does it get back 10.1.2.2, if the dnscache is not > authoritative for it's zone, but rather it just caches > answers it gets from the net, and it can't ever get > the correct answer for 10.1.2.2 from the net???? > > These requests lead to dns timeouts and LAN delays. > > It's important for whatever dns people decide to run to > be able to resolve their masq'd lan names to addresses. > > I don't think that all programs check /etc/hosts. > I don't think /etc/hosts is the correct answer here. > > Apologies for the longish post. It's been bugging me.
As mentioned, dnscache+tinydns will work... Basically, if you REALLY want everything to work properly, you need a DNS server that is authoratative for any local domains (like the private IP space of your internal LAN). Once you have a DNS server configured with this information, you need to specifically tell dnscache about it, since it can't find out about it via normal recursive queries. You tell dnscache about local servers by manipulating files in the /etc/dnscache/root/servers directory (see the notes on my dnscache package page). Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
