On Wednesday, December 8, 2004, 6:02:07 PM, Jon Dossey wrote: >> On Wednesday, December 8, 2004, 5:01:32 PM, Jeff Chan wrote: >> > 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......... >> >> If it helps, I think all the reports have been from FreeBSD >> platforms.
> No no no! I'm sorry, it was totally my fault. Stupid mistake, > corrected now, and it resolves perfectly fine using a local nameserver. > Please don't submit a bug on my behalf, I'm sure the developers are > plenty busy :) > Worth noting is that I don't resolve off 127.0.0.1, I resolve using a > private ip address. OK So is there a (Net::DNS) bug when local resolvers are using 127.0.0.1? I guess I need to read the threads more closely... > By the way, thanks for SURBL Jeff! > Thanks, > .jon On behalf of the many people helping with the project, you're welcome! Jeff C. -- Jeff Chan mailto:[EMAIL PROTECTED] http://www.surbl.org/
