Re: hostname bug by scannig a server.

[<levelzero () retry org>]

The issue here isn't in nmap, but rather in the reverse DNS of your IP
range.

$ host 64.40.106.9
9.106.40.64.in-addr.arpa domain name pointer mail.thrixxx.com.
$ host 64.40.101.176
176.101.40.64.in-addr.arpa domain name pointer mail.thrixxx.com.

Both reverse zones (for 106.40.64.in-addr.arpa and 101.40.64.in-addr.arpa)
seem to be hosted at netnation.com
They can probably set a correct PTR record for your host.

On Wed, 14 May 2008 11:30:34 +0200, Thomas Schneider <komaii () thrixxx com>
wrote:
> hi,
>
> i have installed the new version of nmap-4.62-setup.e** on my windwos
> machine 
> and scanned my server (ip:64.40.106.9) but nmap output gives me a wrong
> hostname.
> --- here the scan:
> Initiating SYN Stealth Scan at 11:20
> Scanning mail.thrixxx.com (64.40.106.9) [1715 ports]
> ---
>
> i don't find where he get this hostname because mail.thrixxx.com is
> 64.40.101.176.
>
> maybe you can help me or tell me what's wrong.
>
> thx,
>
> regards,
> -tom


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