Feature Requests

The DNS query log currently allows 25, 50, and 100 rows per page. Please increase this to include 250 and 500.

Dashboard card showing sites with Zero/low activity for a certain time range. Would like to know which site have Zero Activity if a site has been decommissioned for account cleanup or detecting resolution issues such as DNS filter or if devices have locally set static DNS.

There is no easy way to correlate the devices in the DNSFilter/Zorus portal vs the devices in our RMM that show the software installed (other sources can be used as well). If our RMM shows 800 devices with the agent installed, and the web portal shows 810 devices, how do we identify and correlate the count discrepancy? Right now, this is a manual task. This doesn't scale. What I would love to see is a free-form "asset" field that we can populate with whatever data we want. This needs to be assignable as part of the install process as part of install command line as well as having the ability to update this value after the fact from the endpoint itself (command line tool or registry entry--something accessible by script). This "asset" field would also be visible in the API. With this in place, we could populate this asset field with the RMM device identifier, and then run a script against the API and can have a true 1:1 correlation between the devices in our RMM reporting the software installed vs the endpoints in your portal. Additionally, it would be useful to be able to flag endpoints in the API and then review those flagged endpoints in the web portal. This way, we could review the endpoint status and determine if the endpoint should be deleted or if other actions are more appropriate. FWIW, I performed a variation of this in the Zorus portal by disabling the endpoints in the API for the ones I wanted to review. I was able to review these all at once and it took the administration time for review from 5 hours to about 15 minutes since I didn't have to waste time looking up each and every endpoint individually.

Would like to have a scheduled report to go to a specific client that shows these are the websites that were visited in the last 7 days.

Classic DNS filtering on roaming devices often depended on changing DNS settings. On networks the user doesn’t own—such as hotels, public Wi-Fi, or shared corporate environments—this could cause conflicts with other software and reduce reliability. The new DNS Pre-Check capability modernizes protection by introducing a transparent DNS proxy that validates and filters queries locally before they leave the device. This eliminates the need to modify DNS settings, ensures filtering works across untrusted networks, and helps preserve connectivity wherever users connect. To support this capability, the Windows Agent will include a Filtering & Connection Mode framework. Instead of the agent deciding behavior automatically, administrators can configure three dimensions directly from the Dashboard: Connection Mode: Transparent Proxy or DNS Loopback (how queries are intercepted). Filtering Mode: Classic DNS or DNS Pre-Check (how queries are evaluated). Failover Mode: Fail Open or Fail Closed (what happens if filtering cannot be reached). For ease of deployment, these are also available as presets: Standard (Recommended): Balanced filtering and connectivity. Strict (High Security): Always enforce filtering, blocking access if filtering is unavailable. Custom (Advanced): Mix and match connection, filtering, and failover modes as needed.

Details: Currently, when reviewing users under the MSP Global dashboard, We see just theMSP user accounts for managing clients. To review individual client users and their access levels (Admin, Read only, etc), we have to drill down into each client account separately. Request: Ability to view and export all users across all client accounts from the MSP Global dashboard. Include user access levels in the export for easier auditing and management. This would significantly streamline managing and auditing user permissions across multiple clients/organizations.

We're requesting the ability to approve or deny access to blocked domains directly from the email notifications generated by DNSFilter. Instead of logging into the dashboard, administrators should be able to click through from the notification email to quickly take action (e.g., add to allow list, keep blocked, or submit for review). Customer Value: This would streamline the workflow for IT/security teams by reducing the number of steps required to manage blocked domain requests. It also provides a faster response time for end-users while maintaining admin control and oversight.

Provide the ability to block DNS requests if the domain's destination IP address belongs to a specific country. Allow customers to decide which countries are blocked/allowed in the Dashboard.

I would like to receive an email when I site goes red. I know there are more complicated ways to do this elsewhere, but this would be a great feature to add to future admin email notifications.

Would be useful to have the ability to import custom blocklists (and whitelists) from URLs (for example the ones listed here: https://firebog.net ) and have them refresh at a given interval. This would allow for more fine grained control over ad-blocking etc.