Re: [Nmap-scanner-general] Failure on unresolved DNS

[Max S. <max...@gm...>]

Clayton,

Nice script, I just ran it at home and didn't have that issue, I am
running 4.20ALPHA5, can you try upgrading your version of Nmap to the
latest and see if you still get this error?

I am thinking maybe I should add a "no die on nmap warning" option
that would tell the parser to ignore WARNING messages from nmap ..
somthing like

$nmap->ignore_nmap_warnings();

Sound good to you?

Also, do you mind if I include your script as part of the examples/
directory (with your original comments etc) that are delivered with
the module?

Thanks,
Max

On 11/5/06, Dukes Clayton <Cla...@hc...> wrote:
>
>
>
> Heya,
> Ok, so I have this little utility that scans for port 22,23 and udp/161, but
> it's bombing out on errors.
> Can you recommend a way to make it continue and just mark that host as down?
>
> Here's the result:
>
>
>           Running Total (91 of 2527 devices)
>                         Up: 90          Down: 0
>                         SSH 60          Telnet 31               SNMP 90
> <nmap-error>
>   <pid="6539"/>
>   <cmdline="'/usr/bin/nmap' -v -v -v -sS -sU -v -v -v -p T:22,23,U:161
> --max_rtt_timeout 200 -O
> 03663-3640-1-f-h.kyc.lo.mgmt.medcity.net -oX -"/>
>
>   <nmap-err>Failed to resolve given hostname/IP:
> 03663-3640-1-f-h.kyc.lo.xt.mxty.net.  Note that you can't
> use '/mask' AND '[1-4,7,100-]' style IP ranges
>
> WARNING: No targets were specified, so 0 hosts scanned.
> </nmap-msg>
> </nmap-error>