Richard Collyer wrote:
Daryl C. W. O'Shea wrote:
...
[31974] dbg: dns: name server: 192.168.1.1, family: 2, ipv6: 0
[31974] dbg: dns: testing resolver nameservers: 192.168.1.1
[31974] dbg: dns: trying (3) google.com...
[31974] dbg: dns: looking up NS for 'google.com'
[31974] dbg: dns: NS lookup of google.com using 192.168.1.1 succeeded
=> DNS available (set dns_available to override)
[31974] dbg: dns: is DNS available? 1
192.168.1.1... is that a cable/dsl router acting as your local DNS
server? If so that could explain slow DNS results resulting in longer
scan times for non-local mail.
Yep. Can see why that would slow DNS queries.
I've changed it to a DNS server from my ISP, but so far its not making
any difference.
SA: finished scan in 13.719613 secs - hits=-1.0
For DNS, I'd use a caching name server on the SA host itself that
forwards to your ISPs, name servers.
It's likely that you've got some other net test enabled that isn't fully
configured or broken, like Razor, DCC or Pyzor.
Daryl
