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

Alisa Bailey
  • 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 network-wide deployment, see DNSFilter deployment options.

The Roaming Client and Relay support any DHCP search domain, including multiple domains, passed to the original DNS resolver before the agent or 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.

Caution: Do not install the Roaming Client or Relay on a domain controller. Most domain controllers also act as DNS servers, so a Roaming Client or Relay conflicts with them over DNS traffic. Use DNS forwarding on the network instead, which works well in Active Directory environments.

Web browsers

DNSFilter works in most modern browsers. The following browsers are supported and regularly tested:

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

Support covers the latest release and one prior version of each. Other browsers may work but are not tested.

Windows Roaming Client

The DNSFilter Windows Roaming Client is a Microsoft Installer (MSI) package that can be installed through Active Directory and runs on supported Windows versions. Agent version 2.1.0 and higher supports x64 and ARM64 builds, and requires .NET Framework 4.8.1 or newer and .NET Desktop Runtime 8.0. 

The Roaming Client does not support Windows Server or shared desktop environments. For these environments, use DNS forwarding on the network.

Windows agent support on AWS WorkSpaces, Azure, and cloud VMs

The Roaming Client supports cloud VMs running Windows 10 version 22H2, the final Windows 10 release, or Windows 11.

Non-persistent virtual desktop infrastructure (VDI) environments may show duplicate, offline agents in the DNSFilter dashboard. Use the Clean Up Tool to keep licensing counts and user activity accurate.

Windows 365 Cloud PC

The Roaming Client does not support Windows 365 Cloud PC. Windows agent versions 3.0.x and higher include a Transparent Proxy connection mode that does not rely on DNS loopback, which may reduce some of the compatibility issues seen in earlier releases, where Cloud PC blocked the checks that loopback DNS filtering requires. 

Even with Transparent Proxy, Cloud PC environments can apply network or virtualization controls that interfere with DNS interception, resolver routing, or outbound DNS traffic, so consistent filtering cannot be guaranteed. Testing may be possible, but results vary with the Cloud PC configuration.

macOS Roaming Client

The macOS Roaming Client is a package installer that runs on supported macOS versions. Devices running an earlier macOS version must upgrade the OS before installing the agent.

Chromebook Roaming Client

The Chrome Extension Roaming Client protects managed Chromebooks and Chrome browsers on supported ChromeOS versions.

Android and iOS Roaming Client

The DNSFilter Android app and iOS app protect mobile devices on and off the network. The apps operate a special VPN that forwards DNS queries to DNSFilter but does not forward the rest of the device’s traffic to DNSFilter servers, so that data stays private. The apps run on supported Android and iOS versions.

DNS Relay

The DNS Relay provides DNS protection at the network level and runs on a wide range of operating systems. It is especially useful where a Roaming Client is not available, such as on Linux.

Supported platforms

  • Linux, the recommended option where no native client exists
  • Windows, macOS, or other OS that meets the minimum requirements
  • Virtualized environments, such as VirtualBox, VMware, or cloud VMs

Minimum requirements

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

Notes

Keep the following in mind when deploying the Relay:

  • On some Linux distributions, such as Ubuntu, a local DNS resolver may already use port 53. Disable that service before deploying the Relay
  • The Relay can be deployed as a 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.