Kwirirai wrote:
Hi GuysWin2K caches it's DNS lookups. AFAIK JAMES doesn't. This would tend to invalidate the comparison unless care was taken to ensure that the cache was emptied by restarting the Win2K DNS client service.
I have recently tested out the time it takes to do DNS lookups for James
2.1 release , what I have released it seems to be taking too long for MX record
lookups to be done. On average estimate, it takes about two minutes to do the lookups .
Is there a way that these lookups can be tuned so that the lookups can
take a much shorter time, or does this depend on the network one is using to the lookups ,
or there is some configuration that needs to be done to make it go fast.
I have used nslookup from windows 2000 to lookup records on the same
machine running James
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
