Andrew Roper Thanks for your question! We don’t recommend installing the Roaming Client on servers or domain controllers—this can lead to performance issues and interfere with DNS functionality.For...
Great question, Jeffrey S. Boyd! The good news is you don’t need to add all your locations’ public IPs to a single Site just for Roaming Clients. Roaming Clients work independently of Site IP setti...
Hi Billy , happy to help out! I took a look through Matthew's related ticket, and though they had to shelve the issue and didn't fully resolve it with our support team, I believe the same suggestio...
Saqib Sabir Totally hear you—DoH makes a lot of sense for exactly the reasons you laid out (Chrome and Firefox knew what they were doing!).It’s on our roadmap for Q3, so it’s not forgotten, just wa...
Hi Dax Wiseman , thanks for the question! Here's a basic list to get you started. This is all our filtering categories, with a link to the descriptions housed in our knowledge base. Hope this helps!
Hi there, Saqib Sabir ! Thanks for taking the time to share your experience: great observation and troubleshooting on your part.You're absolutely right that DNS over HTTPS (DoH) fallback could prov...
Great question, Paul Lawler! Scheduled policies in DNSFilter are applied based on the timezone configured for the policy itself, not the timezone of the Roaming Client or the device it’s installed ...
Hi Paul T , thanks for reaching out! If you have access to these machines, you can attempt to make the following changes to re-associate them with your dashboard. Complete Reinstallation: Open the...
Great question, Eric Nix ! DNSSEC validation only occurs when using our DNSSEC-enabled resolvers (103.247.36.9 and 103.247.37.9). The standard resolvers (103.247.36.36 / .37.37) do not perform DNSS...
Hi Kim! I'm totally stumped about why you're getting completely blocked on your individual device, so am going to create a support ticket for you from this post so the team can dig in a little more...