|
/
Zope
/
Apsis
/
Pound Mailing List
/
Archive
/
2006
/
2006-01
/
Pound, DNS lookup, and webalizer question
[
pound 2.0b6 crashes when accessed / Jeffrey Brown ... ]
[
Multi HeadRequire "Host:" directives in ... ]
Pound, DNS lookup, and webalizer question
"Jamie Robe" <robej(at)plancom.org> |
2006-01-25 05:41:16 |
[ FULL ]
|
Thanks to help from this list (thanks Robert) I have gotten Webalizer to
process the logs from pound (syslog with the recommended preprocessing);
however, one issue maybe someone can help me with. I noticed the country
totals is 100% unresolved - like they talk about in one of the FAQs for
webalizer - see snippet below:
----
If you don't enable hostname lookups on your web server, you will get
'100% Unresolved/Unknown' country totals. This is because your log files
only have IP addresses and not names. While it is recommended that you
let your web server handle the DNS lookups, DNS support can be used for
those sites where DNS resolution is not an option.
----
What do I have to do , if anything, on pound to get it to resolve those
IP's? I don't think this is critical for my site, as most of our users
are local to Tampa, Florida USA. However, if it is easy to implement and
won't wreck up my pound service, it might be nice.
By the way, the webalizer graphics are really nice. I put a script in
the cron.hourly to process and update my graphics each hour, and I also
installed boa, a light weight server, on port 8080 - to just feed out my
stats from the pound on port 80. Works good for me, as only internal
users on my network can see port 8080 from the PC in the DMZ.
Jamie T. Robe
Automation Team Leader
The Planning Commission
(813)272-5940
[...]
|
|
|
|
|
Re: [Pound Mailing List] Pound, DNS lookup, and webalizer question
Robert Segall <roseg(at)apsis.ch> |
2006-01-25 10:49:45 |
[ FULL ]
|
On Tue, 2006-01-24 at 23:41 -0500, Jamie Robe wrote:[...]
I suspect you have a poorly configured Webalizer. We use it internally
and IP address resolution was never an issue. To quote from the
Webalizer man page:
REVERSE DNS LOOKUPS
The Webalizer supports reverse DNS lookups through a DNS cache file
that is either created/updated at run-time, or has been previously cre‐
ated, either by a previous run of the webalizer, or by running the
stand-alone version, webazolver. In order to perform reverse DNS
lookups, a DNSCache filename must be specified. In order to cre‐
ate/update the cache file at run-time, the DNSChildren number must be
non-zero. The DNSChildren value specifies the number of children pro‐
cesses to fork, each of which will perform reverse DNS lookups in order
to create/update the DNS cache file. See the file DNS.README for addi‐
tional information.
The "country" pie chart goes by TLD, so once you have correct address
resolution it should work OK.[...]
|
|
|
|