• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

DNS of webpage visitors

A

altexis

Guest
hi all

I want to know if it is possible to find the DNS of the users visiting a webpage.

The apache logs (access_log) contain only the IP.. but is there a place that a DNS is also recorded?
 
in etc/httpd/conf/httpd.conf find
Code: 
HostnameLookups Off
and change to On. Note that this lowers speed somewhat (extra lookup).
 
I see.. thanks AlleyKat.

So I suppose that web statistic programs (like Urchin) scan for changes in the modification dates of access_log and lookup the DNSs themselves? because my server has HostnameLookups Off

Or is there any other more direct way of apache to inform a program when someone visits a webpage?
 
I've no idea about how Webalizer would take this change - in AWstats I can have AWstats itself make the lookups, and thats the only place I want them looked up so thats what I use. Ofcourse it only moves the 'consumes time' problem to AWstats instead (still a better method IMHO), but my logs are easier to read with IP's I think.

So it all comes down to why you need it/what you need it for, you see. :)
 
You must log in or register to reply here.

Similar threads

M
Resolved Forward-confirmed reverse DNS failed tnmpmscs
Replies
8
Views
651
Kaspar
K
burnley
Question granular scope permissions for Plesk REST API
Replies
2
Views
821
burnley
burnley
T
Resolved How to 'selectively' block Mackintosh Chrome browsers
Replies
9
Views
1K
tetrahall
T
D
Forwarded to devs SSL It! / Let's Encrypt DNS-01 challenge remains permanently "Pending" – TXT records created successfully but challenge is never confirmed
Replies
3
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
N
Issue Enabling DNSSec for existing keys -- Workaround for double plesk bug.
Replies
2
Views
462
GCM
G
Back
Top