Re: Context error with --system_dns

[doug () hcsw org]

Hi Sean,

Good find. That's a result of the following change:

o The 26 Nmap commands that previously included an underscore
  (--max_rtt_timeout, --send_eth, --host_timeout, etc.) have been
  renamed to use a hyphen in the preferred format
  (i.e. --max-rtt-timeout).  Underscores are still supported for
  backward compatibility.


Thanks, I'll talk to Fyodor and we'll update that error message ASAP.

What would also be a big help is if you could find the location of
your DNS servers in the windows registry so that the asynchronous
DNS code can find them.

Doug
(Currently testing nmap 4.00 on a big endian architecture)



On Wed, Feb 01, 2006 at 04:13:49PM -0000 or thereabouts, Sean Swift wrote:
> Found a problem with --system_dns setting.
>
> When I tried to scan an IP address on my network with just NMAP
> 192.168.12.45 no parameters I got this error.
>
> Starting Nmap 4.00 ( http://www.insecure.org/nmap ) at 2006-02-01 15:52
> GMT Standard Time
> Unable to determine any DNS servers. Try using --system_dns or specify
> valid servers with --dns_servers
> QUITTING!
>
> When trying to use the --system_dns as instructed by the above error
> message it still did not work and gave me the following error
>
> Unknown long option (system_dns) given@#!$#$
> QUITTING!
>
> After checking "Nmap --Help"  it says to use --system-dns not
> --system_dns
>
> After putting in --system-dns it works fine.
>
> Using Windows 2000
>
> Sean
>
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev


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