Have Apache HTTP server resolve hostnames in logfile on Slackware.

Norwegian · 10-06-2011, 02:14 AM

Like this:

1.2.3.4 customer.43343.someisp.com

bathory · 10-06-2011, 03:27 AM

Hi,

You mean you want to resolve the client's IP? You can do it, but it will slow down your webserver, because it has to contact a dns server to resolve those IPs
Anyway, there is logresolve provided by apache for this.
It's better to use it offline (may through a cronjob) like in the example given in the link above. If you want to resolve client IPs directly, yu need to change CustomLog, like this:

Code:

CustomLog "| /usr/sbin/logresolve >> /var/log/httpd/access_log.new" common

Regards

Norwegian · 10-07-2011, 12:24 AM

Quote:

Originally Posted by bathory

Hi,

You mean you want to resolve the client's IP?

Yes.

Quote:

Originally Posted by bathory

Anyway, there is logresolve provided by apache for this.

What's wrong here:

Code:

root@slackware:/var/log/httpd# logresolve -s statistics -c access_log access_log.new
Usage: logresolve [-s statfile] [-c] < input > output
root@slackware:/var/log/httpd#

bathory · 10-07-2011, 12:45 AM

Quote:

What's wrong here:

Code:

root@slackware:/var/log/httpd# logresolve -s statistics -c access_log access_log.new
Usage: logresolve [-s statfile] [-c] < input > output
root@slackware:/var/log/httpd#

Did you see the logresolve usage? You have to use redirections to the input and output files, like:

Code:

 logresolve -s statistics -c < access_log > access_log.new

Regards

Norwegian · 10-07-2011, 01:36 AM

Thanks for helping me so far

However I get more error messages: (long list)

Bad host: lan-84-240-XX-XXX.vln.skynet.lt != 84.240.XX.XXX
Bad host: pppoeclXXXXXX.minlos.no != 82.116.XX.XX

bathory · 10-07-2011, 02:24 AM

These are dns errors. After doing a reverse lookup for the client IP, logresolve does a forward lookup and finds that they are not the same, so it produces this "error"
You can stop this by omitting the -c switch in the command above.

Regards