On Tue, 1 Oct 2013, Pete Houston wrote:
This reverse resolution will almost certainly be because you are
restricting access to that location (/server-status) by name rather than
by IP address (perhaps inadvertently).
I have
Deny from all
Allow from .triumf.ca
Allow from 142.90.n.m
On Mon, Sep 30, 2013 at 06:03:37PM -0700, Andrew Daviel wrote:
> huh! wtf? - if I enable /server-status, the correct address for the
> client asking for /server-status, is not just logged, but resolved,
> even though HostnameLookups is off. But other requests still get the
> 98.32 address.
This r
On Mon, 30 Sep 2013, John Iliffe wrote:
I'm no expert on this sort of problem but I notice that the first and last
addresses logged both point to:
name = voip-98-144-147-0.wi.rr.com.
name = voip-98-144-141-0.wi.rr.com.
Any chance someone is accessing your web site from a cell phone instant
I'm no expert on this sort of problem but I notice that the first and last
addresses logged both point to:
name = voip-98-144-147-0.wi.rr.com.
name = voip-98-144-141-0.wi.rr.com.
Any chance someone is accessing your web site from a cell phone instant
messaging service?
Regards,
John
===
I'm investigating a problem on an older server, and something strange is
going on. Instead of the correct client address being logged in
/var/httpd/*log, an apparently random address is logged instead.
E.g. 98.144.147.0, 98.208.248.0, 98.144.141.0
Every client is logged as the same address.
