mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
DNS query record filtering #5295
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#5295
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Bitcion on GitHub (Jul 25, 2024).
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to request a feature or enhancement and not ask a question
The problem
When querying DNS records for a keyword, such as "chatgpt," there will be many duplicate records. The effective queries are all records related to the keyword, not just repeated records for one domain. This makes it easier to collect all relevant DNS domains.
Proposed solution
It is recommended to provide an option like "merge duplicate records" in the record type selection.
Alternatives considered and additional information
No response
@tjharman commented on GitHub (Aug 2, 2024):
Can you please clarify - are you talking about the query log?
You say "Querying DNS records" but I think you mean "Querying the log via WebGUI of DNS requests"
Is that what you're talking about? And to also confirm, you're asking so there was prehaps a box called "Show unique entries only" so that apple.com would only be shown once, time.apple.com would only been shown once etc.
How would you propose that timestamps are shown then? No timestamps? A range? Same for clients if multiple clients have looked up that entry how would you propose that should be shown?
It's a good idea for a feature request IMHO I'm just not sure how the details of it would work.
@Zerorigin commented on GitHub (Aug 2, 2024):
In the outer pages, data is grouped by domain and only the last domains is listed.
When an entry is clicked or touched, a hover window pops up or a list expands.
The data in the hover window (or expanded list) is displayed in the current style, but only the current domain is listed.