Webroot® DNS Protection
Welcome to the DNS Protection Discussion Forum!
- 35 Topics
- 192 Replies
Hey! I am having trouble with a popup written DNS unlocker. It keeps popping up, but I know enough not to install it. I am guessing it is some kind of malware or virus and I have read about such malicious things in [url=http://nci.ca/what-can-you-do-to-protect-yourself-from-spyware-malware-and-ransomware/]cyber security blogs on the Internet[/url]. Is this like that wannacry ransomware everyone is talking about? I have webroot installed, but it didn’t give any warning or message about any virus. May be this thing might have escaped its detection. But is it possible? What should I do? Do I need to add any extra protection?
Webroot DNS Protection does gives the option to review unprotected sites. A client at work clicked on continue on an unprotected site, which later downloaded a malware that made files duplicate, had to disallow user from the Domain then next our Response and Detection System. How flexible is it to totally disallow client access to reported malicious websites?
A reply from WebRoot support was made to a ticket I submitted asking how to apply DNS Filtering policies to sites/devices. The answer, in a nutshell, is that there is no applying DNS Filtering policies to sites/devices. The Global Default DNS Filtering policy is it. That policy gets applied to ALL Sites. Even though there are two other policies by default, and new policies can easily be created, they are useless because no other DNS policy other than the Default policy can be applied to anything. Even within one site, it is likely that different devices will require different DNS filtering policies. It is astounding that this product was put into production without this most basic of capabilities. It's not like DNS Filtering is in Beta and we signed on for testing. It's not like this product was just released. The decision by WebRoot to roll out such an unfinished service brings into question the quality of the behind the scenes operations at the company. I have been wrong to assume th
Hello forum members,I hope everyone is doing well. Today, I would like to discuss an issue I've been encountering regarding the compatibility between Webroot DNS Protection and our web filtering software. If any of you have experienced similar challenges or have insights to share, I would greatly appreciate your input.The Challenge:Compatibility between Webroot DNS Protection and Web Filtering SoftwareAs an organization, we understand the importance of web filtering [ https://lenovonetfilter.com/resource/five-common-web-filtering-questions-answered ] to ensure a safe and secure online environment for our users. We have been using a web filtering software solution to control internet access and block inappropriate content. Recently, we implemented Webroot DNS Protection to enhance our overall security measures. However, we have encountered some compatibility issues between these two solutions.Specifically, we have noticed the following challenges:Conflict between Webroot DNS Protection
The block page category function does not work for uncategorized sites. The user and tech had no idea why the page is being blocked. On that if a URL does not resolve there should be a Category as well. People will typo URLs and think the page is blocked when it is just them going to the wrong place.
Already have an account? Login
Login to the community
No account yet? Create an account