On Fri, Dec 28, 2001 at 04:18:06PM +1100, Stilgherrian wrote:
> Looking at the source code, it appears that the default value for
> DNSTIMEOUT is 5 seocnds, so increasing it to DNSTIMEOUT 20 might well
> give you a better result. Indeed, you've piqued my curiosity here, and
> I'm going to run a few tests on some of our hosted sites and see if we
> get better results.
I just ran a few tests, using log files for one of the domains we host.
First, I cleared out all of the entries in /var/analog/dnsfile.txt which
were marked as unresolved. (I'm using Red Hat Linux here, you may have
this file in a different location.) Using this cleared-out DNS cache, I
ran Analog three times: once with the default value, once with a setting
of DNSTIMEOUT 20, and once with DNSTIMEOUT 40.
The percentage of requests from unresolved domains were:
default 45.86%
DNSTIMEOUT 20 42.31%
DNSTIMEOUT 40 42.17%
In other words, increasing the timeout only managed to resolve a few
more domains. My guess is that it's probably not worth changing the
default. Certainly I've heard some ISPs are deciding not to bother to
set up reverse DNS entries.
Of course, if anyone has some hard information here... :)
Stil
--
Stilgherrian, Director of Operations
Taurfish Pty Ltd (ACN 084 970 178)
http://www.taurfish.com.au/
voice +61 2 9331 2737
+------------------------------------------------------------------------
| This is the analog-help mailing list. To unsubscribe from this
| mailing list, go to
| http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
| List archives are available at
| http://www.mail-archive.com/[email protected]/
| http://lists.isite.net/listgate/analog-help/archives/
| http://www.tallylist.com/archives/index.cfm/mlist.7
+------------------------------------------------------------------------
