Webroot® DNS Protection
Welcome to the DNS Protection Discussion Forum!
- 35 Topics
- 193 Replies
Hi All, I am curious what categories we should look at blocking to prevent users from using torrents? I have Security Risk and the Human Resources categories selected. Are there any others that we should key in on. Thanks in advance for any suggestions. Chris
Hi Everyone, My name is Kiran Kumar and I am the Product Director for Network portfolio within the business segment – responsible for DNS-Protection and FlowScape - Network Anomaly detection. I am based in sunny San Diego and have been with Webroot for 4yrs driving various network and Threat Intelligence portfolio. Complementing our award winning Endpoint Protection product, we have put a layered approach in protecting our SMB and MSP clients with a network based solution called DNS-Protection. This is a compelling advantage for Webroot as we look to further establish ourselves as a security leader in the MSP/SMB market and provide a comprehensive security solution and be the trusted security advisor for our MSP/SMB community. Our approach to product development is to bring incremental releases to market and making adjustments based on customer needs and you can find highlights from [url=http://images.saas.webroot.com/Web/Webroot/%7B432250c7-b3c6-45d0-baf9-aba65cf2
We are trialing DNS protection on PC's that are in mobile use all around the country. We've had some interesting results and looking at the DnsProxyAgent I'm a bit confused. Our deploment has devices with WLAN and WWAN (4G module) NIC's operating in public operator network. However in the DnsProxyAgent log file there is no mention of the WWAN module or it's DNS server addresses. Are WWAN NIC's supported by DNS Protection or not? It is the same style NDIS NIC as the others, so here should be no difference. ps. Is there a debug switch that would display more detailed log, for troubleshooting?
Just an FYI to anyone seeking to turn off WebRoot DNS Filtering: My recent experience is that turning off DNS Filtering in the GSM does NOT remove the DNS Filtering agent from the client. I had clients unable to surf due to DNS issues with after DNS Filtering was activated. De-activated DNS Filtering, issues continued. Found the DNS Filtering agent still installed on afftected clients, altering the DHCP DNS settings. Manually removed the agent.
We have to big issue in Turkey to use Dns Protection. In the starting of computers Dns Protection agent cannot resolve any websites like 5 minutes. After 5 minutes Dns agent working properly. This is a very big issue, a lot of customers, and potential customer affected from that problem.
I recently heard about the new SecureAnywhere DNS Protection service. I am looking for an easy to use DNSCrypt solution as I use the open source tools at home, currently. I would like something that can be easily configured to secure my upstream traffic at work. Does the Webroot DNS Protection use DNSCrypt and DNSSEC?
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
In the GSM, a client's site was selected to Manage. On the Site's Management > DNS tab, "Enable SecureAnywhere DNS" was selected. The "Default DNS Policy" field is set to "Default DNS Policy" and is not editable. The attached tag for the field states "...can be modified under Global Settings DNS tab." On the Global Settings DNS tab, there are three existing policies, and new custom policies can be created. However, there is no readily apparrent method to change the Default DNS policy for the site to any policy other than the pre-selected Defaut DNS policy. The Default policy may be edited, but there is no apparent method to change the site default to another existing policy. Further, in the site Policies, "Install DNS Protection" can be turned on for a specific policy, but here also there is no method for applying a specific DNS Policy. Other than editing the Default DNS Policy itself, how does one select or apply a specific DNS policy as default for a site, or
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?
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?
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.