Feature Requests

Dynamic DNS Updating Service provided by DNSFilter

Add support for split DNS in the dashboard. For example allow adding custom A records and CNAME records for internal domains. This would be very useful for networks without an on prem DNS server.

This enhancement request is for a client side tool that could be installed once somewhere on a customer’s network that would report that network’s current IP back to DNS Filter’s servers, thus avoiding the need for a small shop to install a Dyn DNS solution that doesn't otherwise need one.

I would like the ability to add Roaming clients to collections. This way I can more accurately set priority of policies based on collections.

It would be better in my opinion to only show the list of users in the collection versus having all users shown with checks on ones that are in the collection. And if you want to add a user, there can be an "Add User" option which redirects to a list of all users. It would also be nice to show the number of users in a collection in a column in the main Collections page.

For Modems with Mutiple internet sources, We need to add all the static IP's and the dynamic DNS name to sites, however you can't add both as one of the IP's matches the DDNS IP. Please allow for both the IP and the DDNS to be added even if they match. the idea being the IP's witch are static will always be allowed and the dynamic name can resolve any changes/fail over addresses

It would be great if the deployments page would specify how long a site has been offline for. This would be very useful as we would be able to see if a site is merely inactive for a few minutes or if it's been offline for a while and requires attention.

Please improve support for Active Directory groups. It is the primary method of identifying groups of users in Active Directory. Great product if you have a small amount of users. In large enterprise networks, it lacks the ability to apply policies to dynamic groups reliably. We would like to attach Collections to Active Directory groups, and not just Active Directory OUs. OUs do not accurately reflect the groupings for our Internet access filtering needs, but our Active Directory groups and roles do. It is on that basis that we apply our security settings based on user "Role". This way, we need only place Active Directory Users into Active Directory Groups to assign them a filtering policy. Reliable support of Active Directory Groups is one feature missing from what is otherwise a useful security product for us.

Would like a report that gives you agents that have not checked in in 15 days or so.

Right now, if I have a user (non-AD collection) that uses multiple computers, DNSfilter creates multiple user entries for the same user based on the computer name. It would be much better be to be able to have the Users list and collection use the username only. And also be able to add a username manually because right now I have to provision a user, and then have them login and browse the web for a bit so they show up in DNSFilter, before I can add them to their collection, then rinse and repeat for every computer they use. Simply dropping the computer name from the username evaluation and allowing us to manually add usernames would solve this major pain point.