Re: Nmap 4.21ALPHA4 DNS resolve timeout

[Henrik Zagerholm <henke () mac se>]

26 jun 2007 kl. 12:13 skrev Eddie Bell:

> On 26/06/07, Henrik Zagerholm <henke () mac se> wrote:
> > So I get the same result but at a fraction of the time. The script
> > just do 2 things:
> > 1. nmap -sP -n 192.168.1.0/24 (avoiding DNS resolve)
> > 2. Passing the active adresses one by one to nmap again nmap -sL (IP-
> > adress)
> >
> > Done!
> > How can this be?
>
> List scan does not actually ping the host it only makes sure the ip
> address is valid and tries to find the hostname. This is why you
> didn't get the "appears to be up" output for -sL
Sorry for being unclear but the output from my ruby script example is  
regexped so it doesn't return the same input.
The bottom line is that my script is almsot 10 times faster than a  
single nmap call.
How can that be.

Question number 2 is that if I do  nmap -sL 10.0.0.5 and that IP  
doesn't have an entry in the DNS that call takes about 15 seconds.  
How can I set a timeout on this?


> hope this helps
>  - eddie
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org