Last modified: 2013-06-23 18:33:00 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T36438, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 34438 - Reverse DNS lookup
Reverse DNS lookup
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-02-16 09:04 UTC by Félix M. (elfix)
Modified: 2013-06-23 18:33 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Félix M. (elfix) 2012-02-16 09:04:29 UTC 
The current checkuser extension does not show the hostname for each IP.  While it is not too embarrassing (hostnames being easily retrievable), it would save a lot of time for checks on accounts using many different IPs.  

Something like this would be more than fine:

(while viewing a user's IPs)
*  127.0.0.1 (localhost) (check) (block)

or

(while viewing the list of edits per IP or user)
* Link to a page that has been modified
** IP: 127.0.0.1 (localhost) UA: Mozilla/5.0 etc.

Thanks!
Comment 1 Octra Bond 2012-02-16 11:55:50 UTC 
Showing hostname on each IP will make system and network take more time to complete a query. I don't suggest to do that.
Comment 2 Antoine "hashar" Musso (WMF) 2012-02-16 15:23:07 UTC 
(In reply to comment #1)
> Showing hostname on each IP will make system and network take more time to
> complete a query. I don't suggest to do that.

We just need to do an asynchronous name resolution.
Comment 3 Octra Bond 2012-02-17 20:37:40 UTC 
Moreover, AJAX can't connect to DNS directly, ain't it? To make use of AJAX, it must connect to some web-interface resolving service.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links