Re: extra hosts in DNS query

[Daniel Miller <bonsaiviking () gmail com>]

Robin,

Very curious about the segfault, but the reverse DNS number difference is
probably due to your use of traceroute: 61 hosts plus 2 intermediate hops
to be resolved. If you can repeat the segfault, narrowing it to a
particular script or network condition would be critical.

Thanks,
Dan

On Mon, Feb 15, 2016 at 5:00 PM, Robin Wood <robin@digi.ninja> wrote:

> I've just been running a scan and noticed two problems, the first is
> the obvious seg fault, which was a bit annoying, but the second is the
> mis-match in host numbers when the DNS resolution was done.
>
> Stats: 0:17:45 elapsed; 0 hosts completed (61 up), 61 undergoing Traceroute
> Parallel DNS resolution of 63 hosts. Timing: About 98.41% done; ETC:
> 22:52 (0:00:00 remaining)
> Stats: 0:17:55 elapsed; 0 hosts completed (61 up), 61 undergoing Script
> Scan
> NSE Timing: About 87.86% done; ETC: 22:53 (0:00:01 remaining)
> Segmentation fault
>
> This was the command I ran:
>
> nmap -T4 -oA xxx_scripts -iL ips -PN -A -sC
>
> The ips file has 61 entries in it and all through the scan it was
> looking at 61 hosts right up till it did the DNS resolution where it
> jumped to 63.
>
> Running version Nmap 7.01 installed on a fresh Kali box. The box
> doesn't have internet connectivity so I can't easily update it and
> I've only got a limited test window so may not be able to reproduce or
> debug the problem but thought I'd report it in case someone wanted to
> look at it.
>
> Robin
> _______________________________________________
> Sent through the dev mailing list
> https://nmap.org/mailman/listinfo/dev
> Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/