On Wednesday, December 8, 2004, 2:43:48 PM, Jon Dossey wrote: > As per Matthew Romanek's ([EMAIL PROTECTED]) recommendations, I > re-pointed my resolver to a different nameserver (from resolving > locally), and can successfully scan a message in a little under 2.5 > seconds (2.3 - 2.4 seconds).
> I already upgraded to perl 5.8.5 and Net::DNS 0.48, which didn't resolve > the problem. > Does anyone have any idea why it fails when attempting to resolve off > the local nameserver? The resolver works perfectly otherwise. This is strange. I remember there was some talk by the developers of doing something to bypass Net::DNS or do resolution separately. Perhaps did some code for this spill over into the production releases? Or perhaps is there some code for *preventing* this stopping normal resolution when the local resolver serves up on 127.0.0.1? This may deserve a bugzilla......... Jeff C. -- Jeff Chan mailto:[EMAIL PROTECTED] http://www.surbl.org/
