Welcome to the DNS Protection Discussion Forum!
Recently active
The feedback we received from the previous beta was foundational to its success – to the extent that we did not receive one bug complaint or call to Support indicating a problem!! This community is truly awesome! – Thank you!Further feedback mentioned that the previous beta was challenging to participate in as you needed either a trial of DNS Protection or an active Webroot Management Console. We hear you! With this next beta, this time, no Keycode will be required! Simply download and use the Beta Runner! However, if you prefer to use a Keycode you already have, it can be specified.Why a second beta?No software should ever stand still, it must evolve and progress! The second release of DNS Leak Prevention has some awesome new features that further augment Leak Prevention; namely, we have added the ability to dynamically detect DoH servers! Whereas previously we leveraged BrightCloud to provide an up-to-date list, now that is just the foundation to build on - now new DoH servers are de
We are very pleased to announce the launch of the DNS Leak Prevention Beta. This is an opportunity for us to share with you the feature we are about to release, as well as to solicit feedback, both from a technical and functionality perspective. Download the Beta Runner (link removed)Documentation available (link removed) What is DNS Leak Prevention? This is a new patent pending feature of the Webroot DNS Protection product. It is designed to provide control of DNS by blocking all alternate DNS resources aside from those configured in Webroot DNS Protection. This is done by locking down port 53 TCP and UDP (DNS), port 853 TCP (DNS over TLS), and port 443 TCP to known DoH providers. Why are we creating DNS Leak Prevention? As Webroot DNS Protection is a DNS filtering product, if we are not filtering every DNS request, it means that things are being missed. For example, if a web browser were to be configured to get DNS resolution directly from its own server, and disregard what was confi
Hi Team,anyone has any experience implementing DNS protection for users who use VPN (Point-to-site). In my case, it is bypassing the DNS filtring after the VPN gets connected. Tried to play with protected networks feature but no luck. Any experience, tip or advice would be welcome.We have mixture of Azure p2s and Sonicwall global VPN client, both bypass DNS agent.
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
Hello, after i enable webfoot DNS and create dns protection policy i just check social networking , when i apply this policy to site pc’s can not access gmail from any browser what is the reason of it ??
Hi, I tried to enable DNS protection for a macOS device (v10.15.3 Catalina). I noticed there is only a Windows icon on “Install DNS Protection” settings. Does this mean DNS protection is not yet supported on macOS? I checked the docs but couldn’t find anything about this. Is there a way to manually install the DNS protection agent if it is not possible via the policy settings? Thanks for any help.
Hi Where do you manage DNS Protection now in the new console including reports? Thanks
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.
Hi All – I am the Product Manager for DNS Protection and my colleague @JonathanB and I are resident DNS evangelists and we are always interested in hearing from you on your experience with the product – good or bad! It has been close to 2 years since we launched DNS Protection service to the market and I am happy to share that we received the highest rating by Expert Insights and we are seeing good steady adoption of the product. Webroot is committed to serving our SMB and MSP customers and bringing best in class Security offerings. To recap, 2018 was a very busy year for us and I would like to highlight some key product enhancements that has driven our growth: VPN support + IPv6 support (only vendor to support IPv6 for roaming clients) Granular Policy Management enables support at Site, Group, and individual devices. Stable, Hardened DNS client for roaming devices. Powered by BrightCloud Threat Intelligence – Quality, Brand and Accuracy providing Real Time Threat
I need to block all websites except for six that are allowed on the computers. This is a very locked down environment. I don’t see a way to block “ALL websites” and only allow just a handful. wildcards do not work thanks
