Jacques, Thanks for your patience in our offline discussions. My solution does indeed work. However, it's very possible to make your default config work. I made a mistake in telling the tinydns-private server to listen on 192.168.1.254 instead of 127.0.0.1. As a result, dnscache and tinydns-private were competing for the same port on .254. I set tinydns-private back to 127.0.0.1 in my original setup, and it seems to work fine. It's also less effort.
I guess my only recommendation out of all of this is for me to read docs more closely. It could be worth highlighting this potential problem in the tinydns documentation. That is, you say the default 127.0.0.1 is OK. However, you might go on to say that setting it to the internal IP address will collide with dnscache if they're using that, too. Thanks again for the hard work. Daryl --- Jacques Nilo <[EMAIL PROTECTED]> wrote: > Daryl Biberdorf wrote: > > > What about the ports? > > > > From djb doc: > > dnscache listens for incoming UDP packets and TCP connections > addressed to > port 53 of $IP. Typically $IP is 127.0.0.1, but it can also be an > externally accessible IP address. dnscache accepts a packet or > connection > from IP address 1.2.3.4 if it sees a file named ip/1.2.3.4 or > ip/1.2.3 or > ip/1.2 or ip/1. > > JN> $IP is 192.168.1.254 for "external" dnscache > > dnscache sends outgoing packets from high ports of $IPSEND. Typically > $IPSEND is 0.0.0.0, meaning the machine's primary IP address. > > tinydns listens for incoming UDP packets addressed to port 53 of $IP. > It > does not listen for TCP queries. > JN> $IP is 127.0.0.1 for internal tinydns and x.y.z.w for external > tinydns > > Jacques > > ===== Daryl L. Biberdorf [EMAIL PROTECTED] ICQ# 100439225 __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
