Yes, i'm pretty sure there's nothing wrong with it. When using Nslookup from Command Prompt (i'm on windows) and querying against our own domain, it takes about 0.05 seconds to answer back. When querying the same domain with this script, it takes that five to six seconds.
I have the same problem from home as well, with totally different network and using my ISP's DNS server. I've even tested this script on Windows XP and OS X, so i'm really confused here if you get it to answer in a fractions of a second.
In reply to Re^2: Net::DNS::Resolver and very slow reply
by mellin
in thread Net::DNS::Resolver and very slow reply
by mellin
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |