 |  |
>>>>What's PageSentry's timeout limit? If the docs don't say, try asking Maxum.
Re: QDNS server, strange responses pagesentry, etc..
From: Men & Mice Support
Date: Wednesday, November 1, 2000
Time: 6:54:56 pm
>>>
>>>Not sure, but there is no way that I can see to control this from that
>>>particular sentry, ie., the DNS one.. BTW, we also use Netsaint to
>>>monitor our network, and it is plugging out the same alert messages... At
>>>least with NetSaint I can boost the time out.
>>
>>Never heard of Netsaint before. What's its timeout setting currently?
>
>NetSaint is a Linux variant kind of like a pagesentry, but a whole lot
>more full featured. We have the time out at about 60 seconds. I will
>boost this a bit.
60 seconds is far too long. The timeout shouldn't be longer than 15
seconds, and should probably be set to 7.5 seconds or even less. If
the server isn't responding in under 2 second to a request for
information it already knows, then it's not able to service incoming
requests in a timely manner. Most TCP/IP stacks give up after 7.5
seconds, and most resolvers will have to make at least 2 queries to
resolve an average name.
>Perhaps it is the level of dialup subscribers we have?
Yes, that's quite possible.
I would suggest that hosting 3000 domains and using the server for
recursive resolution for a large number of dial-up customers is
possibly going to stretch the capabilities of the server.
However, if the server's still responsive, you may not need to split
the two types of service. You may want to test, though, to make sure
it isn't dropping requests or otherwise not performing as well as you
require.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
Messages In This Thread:
Return to Digital Point Solutions' Home Page