Feature Requests

Microsoft, and many other hardware vendors, are building their next-gen hardware models with Qualcomm Snapdragon processors. Please provide support for these hardware platforms.

Would like the ability to initiate an uninstall of the Windows roaming client from the DNSFilter dashboard.

We have a number of macOS devices that we would like to update but DNSFilter Agent is not yet officially supported.

We need to be able to specify 2-3 users as "Owner" level so we are able to have redundancy of this function across our 25+ engineers.

Can you add Roblox to AppAware to enable blocking? Just heard stats from a law enforcement presentation that the FBI has identified it as the number one way sexual predators now target children.

Can we add more tools to the "remote desktop" AppAware library. Right now, we do have a bunch of other tools that we would like to block, such as splashtop, teamviewer, etc, but it's odd that only one app is listed as an option.

An improvement where all reports and links are fully whitelabeled, ensuring no DNSFilter branding is visible. This includes removing any references or hyperlinks that directly reference DNSFilter, allowing customers to present the reports entirely under their own brand identity. Scheduled reports currently have DNSFilter footers and e-mail layout that is not suitable for distributing externally, unless we save the document and cut out the footer to send it manually.

I work for an MSP organization and across our deployment of roughly 8k agents the Block Request form has been working as expected. Over time though, we have discovered instances of a block request investigation where it would be useful for the following features in the Block Request Form. While I can understand that our current naming scheme of a short-code may not have been the best naming convention initially, I don't want to start manually re-naming every policy if it could be helped. -(A) the host-name of the roaming client where the request came from if applicable -(B) the organization the roaming client was either installed under or the organization that the referenced filter policy is located under. Example situation for requested features: During a recent block request investigation, the tech performing the investigation discovered that the roaming client appeared like it was installed incorrectly under a different organization based off the filter policy flagged. With no global way to search for a specific roaming client to see where it was, the tech determined that the best course of action was re-installing the roaming client which resolved the issue.

I've created a filtering schedule to limit access to social media sites during the workday starting at 9am however the social media sites specifically twitter continue to work for quite a while after 9am because of cached results

Often when a support case is raised, DNSF support asks for agent logs, which is somewhat of a manual process. We're requesting a feature where logs can be "fetched" from roaming clients via the DNSF portal so that the logs are more easily visible to us and DNSF support. This approach would remove the need for running batch files on the roaming client and needing to attach ZIPPED logs to tickets. DNSF Support would be able to begin troubleshooting a problem as soon as a support issue is raised.