I'm trying to figure out why I'm having ridiculous scan times such as the above examples. Lower scan times such as in the 20 second range are the exception rather than the rule. I'm running bind as a local caching nameserver and it seems to be working correctly. I've just seen a ham that has a scantime=172.2. Could there be something else on the system that is affecting this?
Any advice as to troubleshooting would be appreciated. -- Chris KeyID 0xE372A7DA98E6705C
signature.asc
Description: This is a digitally signed message part
