Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Advanced query log view #2223

Closed
Dubz opened this issue Oct 26, 2020 · 3 comments
Closed

Request: Advanced query log view #2223

Dubz opened this issue Oct 26, 2020 · 3 comments
Labels
duplicate Duplicate or merged issues.

Comments

@Dubz
Copy link

Dubz commented Oct 26, 2020

Problem Description

Tracing domain issues/blocks is not as easy as it could be. Right now I have to check multiple places to try and find what might be being blocked, and maybe not even know what I'm looking for (I could find out if I was on site personally, but remote troubleshooting is a tad more cumbersome with AdGuard than PiHole is.

Proposed Solution

Expand the query log to a more advanced view. Have a column for DNSSEC validation, and another for block reasons (ad list, malware list, custom blacklist, external DNS block, etc). Additionally, expand the search capabilities on this page (for example, to be able to find DNSSEC failures).

Alternatives Considered

PiHole currently has this in their log, although not separated, but there nonetheless. I'd prefer to switch to AdGuard long term if possible, as it has some capabilities built in to it (such as DoH/DoT clients and servers) that PiHole does not.

@ameshkov ameshkov added the duplicate Duplicate or merged issues. label Oct 26, 2020
@ameshkov
Copy link
Member

Please try the beta version and check what we've done there, most of the requested features are there already.

If there's some filters/details missing, please file a feature request that lists what you'd like to have, but please make it as detailed as possible.

@Dubz
Copy link
Author

Dubz commented Oct 27, 2020

@ameshkov I just deployed the beta version to see the difference, however the query log page looks the same as before. The only difference is, the select dropdown options are fixed in the beta version to not show a blank option. The rest of the query log, however, is the same.

Ideally, I think the simplest solution would probably be to add response codes as a searchable term. So if I search for SERVFAIL codes, I should be getting back domains that failed DNSSEC validation.

Additionally, with DNSSEC validation enabled, the green lock on the left should not show as such. There should be a broken lock that's red, causing more attention to be drawn to this domain. It may have been validated, but it didn't pass.

@ameshkov
Copy link
Member

Filed a new FR, please upvote: #2226

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Duplicate or merged issues.
Projects
None yet
Development

No branches or pull requests

2 participants