tldlookup does lookup the top level domain, so if an NSlookup for an IP returns bushnet.co.ug it will recognize the IP as a ugandan one. For bushnet.net, it will assign it to the .net cloud, which is non-locatable geographically.
so the list in the first email is IP's that are not resolvable using NSLookup. (And yes, for me at least, the nslookup to the bushnet IP 41.220.0.121 fails, note that i am in their network, so my config is a bit different than from a website on the web) As McTim (your mail just came in, thanks) states, even if you have a .net .com or .org top level domain, its still unclear where the source network is located (again, like bushnet.net) joomlastats (the tool i use) then uses the RIPE whois function. I took a quick look at that website, and here i again get lost and require some proper knowledge. Can you shed some light as to how that works? Do they use the actual address of the owner of the domain? In the meantime, I (and i guess with me, some others) would appreciate if all of you who manage routers/proxy servers would make these NSLookupable (is that still english, like googling?) rgds, reinier PS Post about how 'The Tool' is doing it: http://www.joomlastats.org/component/option,com_joomlaboard/Itemid,/func,view/catid,8/id,2307/#2307 RIPE website http://www.ripe.net/ On Monday 31 July 2006 13:02, Reinier wrote: > Hi guys, > > i'm trying to follow the current discussion, very very technical stuff. I > have a question that might be related. > > I have some software that monitors the usage of my websites. The software > does a tldlookup, in order to locate the source of the requests. If it finds > the location, it can show nice graphics of where the webtraffic is coming > from in the world. > > some of the statistics look like: > > 81.199.17.218 --> unknown --> 81.199.17.218 > 41.220.0.121 --> unknown --> 41.220.0.121 > 193.108.254.83 --> unknown --> 193.108.254.83 > 41.220.0.121 --> unknown --> 41.220.0.121 > 81.199.17.194 --> unknown --> 81.199.17.194 > 195.229.89.29 --> unknown --> 195.229.89.29 > 65.222.185.75 --> unknown --> 65.222.185.75 > 81.199.17.182 --> unknown --> 81.199.17.182 > 81.199.18.102 --> unknown --> 81.199.18.102 > 204.10.227.2 --> unknown --> 204.10.227.2 > 81.80.243.234 --> unknown --> 81.80.243.234 > 196.25.34.23 --> unknown --> 196.25.34.23 > 65.160.238.180 --> unknown --> 65.160.238.180 > 196.41.37.211 --> unknown --> 196.41.37.211 > 204.246.129.196 --> unknown --> 204.246.129.196 > 193.108.254.83 --> unknown --> 193.108.254.83 > 82.206.143.43 --> unknown --> 82.206.143.43 > 41.220.0.121 --> unknown --> 41.220.0.121 > 193.108.254.83 --> unknown --> 193.108.254.83 > > > I notice that bushnet is there, unresolved, and maybe some other ugandan > sources as well. Who would be the people to enable the succesfull tldlookup? > Is that the owner of the domains? The configurator of the respective > proxy-server? > > These stats are very usefull for webmasters. For a sample, take a look at > http://www.joomlastats.org/ > > rgds, > reinier > _______________________________________________ > LUG mailing list > [email protected] > http://kym.net/mailman/listinfo/lug > %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ > > The above comments and data are owned by whoever posted them (including > attachments if any). The List's Host is not responsible for them in any way. > --------------------------------------- > > _______________________________________________ LUG mailing list [email protected] http://kym.net/mailman/listinfo/lug %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ The above comments and data are owned by whoever posted them (including attachments if any). The List's Host is not responsible for them in any way. ---------------------------------------
