General setup notes: eth1 is my internal network 192.168.0.1 ppp0 is my external dsl dial up connection
I'll break down changes based on packages.
dnscache: internal IP changed to 192.168.0.1 Querying hosts 192.168 and 127.0.0.1
tinydns: private, internal dns 127.0.0.1 private dns server list: .private.network::localhost .0.168.192.in-addr.arpa::localhost @private.network::mail.private.network =firewall.private.network:192.168.0.1 +gateway.private.network:192.168.0.1 =fidget.private.network:192.168.0.21 +olympian.private.network:192.168.0.21 =solfish.private.network:192.168.0.13 =sentient.private.network:192.168.0.7 +www.private.network:192.168.0.7 @mail.private.network:192.168.0.7
Declared domains: private.network 0.168.192.in-addr.arpa
shorewall: Ifaces: #ZONE INTERFACE BROADCAST OPTIONS net ppp0 - routefilter loc eth1 detect dhcp
Rules relating to dns (perhaps need loc fw same rules?): # Accept DNS connections from the firewall to the network # ACCEPT fw net tcp 53 ACCEPT fw net udp 53
Masquerade: #INTERFACE SUBNET ADDRESS ppp0 eth1
Config: CLAMPMSS=yes
On Sun Nov 23 11:51:22 EST 2003, Eric Spakman <[EMAIL PROTECTED]> wrote:
Hey everyone,Raymond,
I'm using Bering-uClibc 2.0 and setup tinydns and dnscache on it. However I'm having a problem where after about 5-10 minutes dns lookups fail. If I restart dnscache from init.d things go back to normal. I was wondering if anyone here might be able to help me out with this problem.
I'm not sure if this is related, but ntpdate has been unable to talk to servers like time.nist.gov says there's a sendto error. Also ez-ipupdate fails to connect members.dyndns.com:80.
Could these be related, and might they have something to do with a misconfiguration of shorewall?
Appreciate any insight
-- Raymond Page
You don't give much insight on your setup (dsl, cable, dialup, ...), configuration items you changed (dnscache, tinydns, shorewall, ...) so I can only guess. When dnscache fails things like ntpdate and ez-
ipupdate don't work anymore because they can't resolv the hostnames anymore, so that is expected. The question is why dnscache suddenly dies.
You can do some trouble shooting by looking at the output of "shorewall hits": are there local ports that get blocked which shouldn't. The output of "df" and "free": aren't there any memory problems. With ps you can see if the dnscache daemon is still running at the time you have problems. And ofcourse by looking at the various files in /var/log.
Regards,
Eric Spakman -------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
------------------------------------------------------------------------
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
-- Raymond Page
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ------------------------------------------------------------------------ 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
