Reverse DNS lookup
Open, MediumPublicFeature
Actions

Assigned To

None

Authored By

	Elfix
	Feb 16 2012, 9:04 AM

Description

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)

(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!

Version: unspecified
Severity: enhancement

Details

Reference: bz34438

	Title	Reference	Author	Source Branch	Dest Branch
	data-engineering: Allow git-sync image to build on trusted runners	repos/releng/gitlab-trusted-runner!91	bking	git-sync	main

Customize query in GitLab

Related Objects
Search...

Status	Subtype	Assigned	Task
Open		None	T139810 RFC: Overhaul the CheckUser extension
Resolved		Niharika	T236225 [Epic] CheckUser 2.0 Improvements
Resolved		Niharika	T237593 [Epic] CheckUser 2.0: Compare
Stalled		None	T179459 Enhance blocking in AbuseFilter
Stalled		None	T179454 AbuseFilter range blocks should be smarter
Declined		None	T175160 Identify the source of WHOIS data, the retrieval method, and update frequency
Open		None	T174388 LoginNotify should inform users of the IP address of failed login attempts to their account
Declined		None	T152114 Show provider and country for IPs in Special:RangeContributions
Resolved	Feature	None	T18068 New page: Special:Whois / Special:AboutIP
Open		None	T174553 Create a mechanism that allows fetching geolocation and subnet data for IP addresses
Open	Feature	None	T36438 Reverse DNS lookup

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 22 2014, 12:17 AM

• bzimport added a project: CheckUser.

• bzimport set Reference to bz34438.

• bzimport added a subscriber: Unknown Object (MLST).

Elfix created this task.Feb 16 2012, 9:04 AM

Showing hostname on each IP will make system and network take more time to complete a query. I don't suggest to do that.

(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.

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.

Would the user's ISP be able to tell that they're being checkusered through this? I wonder if that would be problematic.

Restricted Application added subscribers: JEumerus, Aklapper. · View Herald TranscriptFeb 7 2016, 4:25 PM

hashar unsubscribed.Feb 7 2016, 11:02 PM

MarcoAurelio mentioned this in T139810: RFC: Overhaul the CheckUser extension.Jul 23 2016, 1:26 PM

MarcoAurelio added a project: Stewards-and-global-tools.Jul 23 2016, 1:43 PM

MarcoAurelio removed a subscriber: • wikibugs-l-list.

Liuxinyu970226 subscribed.Jul 27 2016, 3:25 AM

Matanya moved this task from Untriaged to Medium priority on the Stewards-and-global-tools board.Apr 19 2017, 7:51 PM

T174553 will solve this.

Meno25 unsubscribed.Nov 23 2018, 7:51 AM

• Demian added a parent task: T174553: Create a mechanism that allows fetching geolocation and subnet data for IP addresses.Nov 6 2019, 8:35 AM

• Demian mentioned this in T237486: Organize tasks related to the overhaul of CheckUser.

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 12:24 PM

Reverse DNS lookupOpen, MediumPublicFeatureActions

Description

Details

Related ObjectsSearch...

Event Timeline

Reverse DNS lookup
Open, MediumPublicFeature
Actions

Related Objects
Search...