You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I would like to suggest two improvements for the DNSCrypt‑Proxy Web UI (port 8080) used on a high-load system.
REJECT filtering / separate view
Currently, all DNS queries (PASS + REJECT) are displayed in one table.
With large blocklists, REJECT entries flood the view and make it difficult to monitor new or allowed (PASS) queries.
Proposed improvements:
Optionally split into separate tabs: “Allowed” / “Blocked”.
Cache statistics accuracy
The Web UI currently includes all queries when calculating cache hit ratio.
However, blocked (REJECT) queries are never cached, so including them inflates/misrepresents cache statistics.
Proposed improvement:
Only successfully resolved queries (PASS) should contribute to cache hits/misses.
Benefits:
Improved real-time monitoring of allowed queries.
Accurate cache efficiency statistics, especially important with heavy blocklists.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I would like to suggest two improvements for the DNSCrypt‑Proxy Web UI (port 8080) used on a high-load system.
Currently, all DNS queries (PASS + REJECT) are displayed in one table.
With large blocklists, REJECT entries flood the view and make it difficult to monitor new or allowed (PASS) queries.
Proposed improvements:
Add filter buttons: “ALL”, “PASS only”, “REJECT only”.
Option to hide REJECT entries by default.
Optionally split into separate tabs: “Allowed” / “Blocked”.
The Web UI currently includes all queries when calculating cache hit ratio.
However, blocked (REJECT) queries are never cached, so including them inflates/misrepresents cache statistics.
Proposed improvement:
Only successfully resolved queries (PASS) should contribute to cache hits/misses.
Benefits:
Improved real-time monitoring of allowed queries.
Accurate cache efficiency statistics, especially important with heavy blocklists.
Beta Was this translation helpful? Give feedback.
All reactions