Feature Requests

As an admin, I would like the ability to stop users from uninstalling the DNSFilter macOS RC. This would be for users who have admin accounts on the computer.

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

We would like to see automatic Site/Policy and roaming client association implemented based on the IP of a roaming client. For example, if a roaming client connects from a private network (IP SMARTWORKING) it should be automatically associated with the “IP SMARTWORKING SITE.” Conversely, if a roaming client connects from a corporate network (IP CORPORATE Y) it should be automatically associated with the “IP CORPORATE Y SITE” site. This would help to figure out which site each roaming client is in and then define site-specific policies for each site. A default site could also be created if the roaming client does not connect from a defined IP. Currently, there is no automatic association between a roaming client's IP and a site defined in DNSFILTER.

in a modern company you usually support linux as an operating system as well so it would be great to have dns filtering also available here, without much hustle during the installation

We are wondering why the auto update feature is moving so slow across our fleet of roaming clients and noticed that the roaming client auto update feature has this text about checking for updates every day at 12:00 GMT. Updates from 1.6.2 to 1.8.2 has taken months and we are not fully updated yet across our fleet. Is this true to understand that updates are only checked at the same hour every day? What if our org is across 6 or more timezones internationally and some of our roaming clients are offline at that hour, will those roaming clients never check for updates? Does a roaming client check for updates as soon as it wakes up with activity? The feature request I am considering here is a button for us to be able to force updates on selected devices, or all devices if the case of checking for auto updates are only at 12:00 GMT every day.

Similar to https://dnsfilter.canny.io/feature-requests/p/duplicate-roaming-clients-in-dashboard and the merged post in that thread: We still see duplicate macOS devices which leads suspicion that agents are not using any unique identifiers tied to a host? I recently uninstalled the package on my own device, reinstalled it and now theres an offline host and an online host in my inventory. How do we ensure that the 'Clean Up Roaming Clients' feature knows which host by hostname to clean up if it only shows 1 host out of the duplicate roaming clients and does not harm the other host which has the same mac address for example?

It would be ideal to be able to toggle an "auto uninstall" per client and set a policy to remotely delete agent that doesn't check in within 30, 60 or 90 days. Our RMM auto installs DNSFilter so it is an easy re-add if needed. But this would help us keep our counts up to date.

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

Website history

At this time in order to use the iOS Roaming Client, it needs to be on a device that is in supervised mode using an MDM. Requesting ability to use DNSFilter iOS Roaming Client on Unsupervised devices (in a BYOD scenario for companies wishing to extend the DNSFilter protections to personal devices).