192.168.x.x/16 is the private space (RFC 1913).  So no public facing DNS
server would resolve those.  It would only be resolved if you were pointing
to your internal DNS server AND it was setup to manage the specific zone.
So the question is where is nslookup getting names from?



-----Burton

%QUOTE%

-----Original Message-----
From: ntop-bounces@list...
[mailto:ntop-bounces@list...] On Behalf Of Charles Gagnon
Sent: Tuesday, September 27, 2011 1:12 PM
To: ntop@list...
Subject: [Ntop] DNS Resolution half working

I searched for references and I can't find what this error could be.
When listing hosts (specially in the throughput list I use a lot), some
hosts get resolved and others don't and I can't figure out why.
I've setup DNS resolution to 'All' (though I tried "local" and "Local
+ Remote").

When I look at the list, a number of items have names, others should the IP
with "[IP]" after. Seems very consistent, the same hosts are resolved and
the same show IPs between restarts.

I was thinking of flushing out dnsCache.db but I don't that exists in
4.1.0 (gone since 3.x maybe?).

When I dump the hosts, I see some with names and others without:

192.168.206.11|0|'192.168.206.11'|'192.168.206.11'|[...]
192.168.206.10|0|'192.168.206.10'|'hhnas01'|[...]
192.168.206.13|0|'192.168.206.13'|'192.168.206.13'|[...]
192.168.206.12|0|'192.168.206.12'|'192.168.206.12'|[...]
192.168.206.15|0|'192.168.206.15'|'hhutil01'|[...]
192.168.206.14|0|'192.168.206.14'|'192.168.206.14'|[...]

Any ideas? Any other "cache" I can get rid of. Testing with nslookup yields
a name for all those IPs.

--
Charles Gagnon
charlesg at unixrealm.com
_______________________________________________
Ntop mailing list
Ntop@list...
http://listgateway.unipi.it/mailman/listinfo/ntop

_______________________________________________
Ntop mailing list
Ntop@list...
http://listgateway.unipi.it/mailman/listinfo/ntop