martin f krafft wrote:
also sprach Simon Kelley <[EMAIL PROTECTED]> [2006.07.10.1130 +0200]:
. Even if it were, dnsmasq throws away servers with addresses it's
listening on so the 127.0.0.1 entry isn't a problem. To get a server
loop, you should need at least two servers forwarding to each other.
Ah, okay this is good.
The forwarding table overflow message is generated when there are at
more than 150 unanswered queries less than 20 seconds old. It's easy to
get this with a loop, where the same query bounces around forwever, but
it's possible to get it in other ways too. A high query load into
dnsmasq and a forwarding to a slow or flaky server will do it: the
favourite way is running one of the applications which do bulk-lookups
of IP addresses to fill in webserver logs.
Can you give a few more details on the exect problem: is it intermittent
for not? What sort of load are you using? What does dnsmasq log about
the servers it's using at startup?
Exactly that... web server logs. Can I tweak these limits?
Yes, but only with a recompile.
src/config.h, edit FTABSIZ and TIMEOUT
Cheers,
Simon.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
