On Friday 26 December 2003 10:15 pm, Ray Olszewski wrote: > Since most of the detail in your latest message is about how you did get > things working, I'll skip over that to the one problem that remains -- > reverse lookup of on-LAN IP addresses. The tcpdump output says that the > mail server is querying a DNS server that does not exist. Edited to > highlight what matters, the attempt is reflected in several exchanges that > have this form:
The big catch to running both tinydns and dnscache together is that they may not work correctly if they are both bound to the same ip address (and is generally stated as such in the available configuration docs). The fix is to bind dnscache to localhost (127.0.0.1) and tinydns to your LAN interface(s) (192.168.1.254, etc...). This is a possible conflict that can cause similar problems due to the two applications getting confused on who is answering the request. -- ~Lynn Avants Linux Embedded Appliance Firewall Developer http://leaf.sourceforge.net http://guitarlynn.homelinux.org:81 ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ------------------------------------------------------------------------ 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
