For me, Webalizer 1.30's stats show "Unresolved/Unknown (100%)" under the Usage by Country tab. How do I get it to actually say 25% US, 5% France, and so on?

Thank you, and yes I know this is an old version of Webalizer, but it seems to do everything I want so I'm not bothering to upgrade. :D

Even my Webalizer 2.01 doesn't show this info correctly...

It does this bases on the domain name of the requestor. With the old webalizer you'd have to turn on domain name resolution for the apache logs. For the new one I think you can have webalizer do the resolution as it generates the logs.

IMHO this is a fairly useless feature since most of your users will come from .com which really doesn't tell you anything.

since most of your users will come from .com
Forgive me, but what a complete nonsense! Not everyone lives in the USA...

I have actually turned on domain name resolution in my apache logs. Maybe it's just a feature they never got around to implementing properly...

Not everyone lives in the USA

I know that. What I meant is that .com is not indicative of a given country. Anyone anywhere can be using a .com name.

On my previous host that resolved names the country graph worked just fine. As it is I get better country stats by running Burst banners. They resolve the ip address to a given country (rather than assuming .com is US) and therefore give much more accurate results that webalizer could.

Why not try some tracker services. for example, thecounter.com. Sometimes it's a little slow, but you do get somewhat country info. The best thing I like is you can choose a transparent style so it will not interfere your web design.

ebird

Originally posted by avara
I have actually turned on domain name resolution in my apache logs. Maybe it's just a feature they never got around to implementing properly...

I suggest against using this practice. This will generally slow down your HTTP requests by 1-2 seconds, as the server makes the reverse-dns request.

Either use some tool to do it after (as latests versions of webalizer do) , or use an external tracking service.

Originally posted by Félix C.Courtemanche


I suggest against using this practice. This will generally slow down your HTTP requests by 1-2 seconds, as the server makes the reverse-dns request.

Either use some tool to do it after (as latests versions of webalizer do) , or use an external tracking service.

I've turned it off now. :cool:

I used to use Webalizer, but now use Awstats, which works on the same principle as webalizer, by using the apache log file to generate stats, and they actually work. Tells you which hosts, what country etc....

All it is, is a bunch of perl scripts....

Need a link or the software email me imran@cabalstudios.com