Skip to main content

How can we help you?

Search

help Knowledge Base
forum Community
checklist Release Notes
event Events

Supported Operating Systems and Web Browsers

Minetta Gould
  • Updated

    In this article

This article outlines the operating systems supported by the DNSFilter Roaming Client and Relay, as well as web browsers for app dashboard navigation. For details on network-wide deployment, see the Network Deployment Options guide.

Both the Roaming Client and Relay support any DHCP Search Domain (including multiple domains) passed to the original DNS resolver before the agent/relay takes over. Local domains and predefined lists continue to resolve through the original DNS server unless otherwise configured.

Use the Roaming Client for supported endpoints, or the DNSFilter Relay for network-wide and Linux deployments.

We do not recommend installing the Roaming Client or Relay on a domain controller.

Most domain controllers also act as DNS servers for the network, meaning they’re already handling name resolution. Adding a Relay or RC on top can create conflicts, since both services attempt to manage DNS traffic simultaneously.

Instead, use Network Deployments to forward DNS traffic — this works especially well in Active Directory environments.

Web Browsers

DNSFilter works in most modern browsers, but we officially support and regularly test:

  • Google Chrome
  • Microsoft Edge
  • Mozilla Firefox
  • Apple Safari

We support the latest release and one prior version of each. Other browsers may work but aren’t part of our testing cycle.

Windows Roaming Client

The DNSFilter Windows Roaming Client is a Microsoft Installer (MSI) package and can be installed via Active Directory. 

The Windows agent supports Windows 10 or newer (x64) /w .NET Framework 4.8 or higher. Agent version 2.1.0 and higher supports x64 and ARM64 builds, and requires .NET Framework 4.8+ and .NET Desktop Runtime 8.0. 

We do not support Windows' Server OS or shared desktop environments of any kind with our Roaming Client. We recommend utilizing DNS Forwarding for the network to keep it protected.

Windows agent support on AWS WorkSpaces/Azure/Cloud VMs

Only the Windows 10 OS (final version rollout update) 22H2 release would support Roaming Clients on Cloud VMs. The Windows 11 OS supports the Roaming Clients already, as it is originally included in the 22H2 update.

Environments operating non-persistent Virtual Desktop Infrastructures (VDIs) may encounter duplicate, offline agents listed in the DNSFilter dashboard as a result. Utilize the Clean Up Tool to maintain accurate licensing counts and user activity. 

Windows agent support on Cloud 365 PC

Windows 365 Cloud PC is not a supported endpoint environment for the Roaming Client. In our newer versions (2.2.x and higher), the client performs stricter IPv4 connectivity checks. Because Cloud PC blocks these checks by default, the client does not apply the loopback address, which is required for DNS filtering to work.

If you wish to test or use the client in this environment, you can work around the issue by either:

  • Manually setting 127.0.0.1 as the DNS server on the network adapter, or
  • Allowing outbound TCP traffic on ports 443/853 to our resolvers: 103.247.36.36 and 103.247.37.37

Note: these steps are considered a workaround only. Since Cloud PC is not a supported platform, we can’t guarantee consistent behavior or provide ongoing fixes for this environment.

macOS Roaming Client

The DNSFilter macOS Roaming Client is downloaded as a Package Installer. 

The macOS Roaming Client supports:

Chromebook Roaming Client

The DNSFilter Chrome Extension Roaming Client allows you to protect Chrome devices like managed Chromebooks and Chrome browsers.

Android and iOS Roaming Client

The DNSFilter Android App and iOS App protect roaming mobile clients on and off the network. 

The apps operate a special VPN which forwards DNS queries to DNSFilter but avoids forwarding the rest of your traffic to our servers–the privacy of your data is ensured.

DNS Relay

The Relay provides DNS protection at the network level and can run on a wide range of operating systems. It’s especially useful for environments where a Roaming Client is not available (such as Linux).

Supported Platforms

  • Linux (recommended solution where no native client exists)
  • Windows, macOS, or other OS that meet the minimum requirements
  • Virtualized environments (e.g., VirtualBox, VMware, cloud VMs)

Minimum Requirements

  • 64-bit, 2-core CPU
  • 2 GB RAM

Notes

  • On some Linux distributions (e.g., Ubuntu), a local DNS resolver may already use port 53. Disable this service before deployment
  • The Relay can be deployed via Docker container or as a standalone binary
  • If a Relay fails to start, check for conflicts with other local resolvers

Comments

3 comments

Date Votes
  • Charles Jones

    The .NET requirements needs some clarification or correction. There are 3 possible .NET runtime packages per https://dotnet.microsoft.com/en-us/download/dotnet/8.0 :

    ASP.NET Core Runtime

    .NET Desktop Runtime

    .NET Runtime

    The only package with “Core” in the name is the ASP.NET package, which is for servers and web hosting.

    0
  • Charles Jones

    Also, it is called out that both .net Framework 4.8+ and .net Core Desktop 8.0 are required. Is this the case? Do we need to install both of these packages for agent 2.1.0?

    0
  • Minetta Gould Community Team DNSFilter Staff

    Great catch, Charles Jones—and thanks for flagging this! 🙌 We’ve updated the article to clarify the .NET requirements.

    To confirm:

    • You’ll need .NET Framework 4.8.1 and .NET Desktop Runtime 8.0 for agent versions 2.1.0 or 2.2.1
    • The reference to “.NET Core Desktop 8.0” was incorrect—the correct package is .NET Desktop Runtime 8.0 (not ASP.NET Core)

    Appreciate you helping us keep the documentation sharp!

    0

Please sign in to leave a comment.