We've given the Sites section in your DNSFilter dashboard a complete makeover! This update brings a fresh look that's easier on the eyes and introduces powerful new features:

Sleek New Design: The Sites section now boasts a modern, streamlined look that matches the rest of your dashboard experience.

Enhanced Organization for Multi-Tenant Accounts: If your are an MSP or Multi-tenant user , you'll appreciate our new global site management capabilities, making it easier to oversee and manage you sites across all your organizations. You now have the ability to manage and search through all sites across all your organizations from a single page, enabling you to manage your vast word

Improved Search: Quickly find if a specific IP is in use across all your sites. If it is, easily determine what site it is currently associated with

Optimized Workflows: Adding, editing, and tracking your sites is now more efficient, especially for organizations with many sites and IP addresses, ensuring smooth performance.

We’ve rolled out a brand-new Chrome extension built on Manifest V3, packed with improvements for ChromeOS users.

This update is currently available as a Beta Release and .

To get started:

💬 We’re actively gathering feedback—so if you’re testing the beta, let us know what you think!

🔐

Built on Google’s Manifest V3 standard, this update brings:

🎨

🏢

A new version of the is now available! You can download updated binaries from the DNSFilter Dashboard () or refer to our Help Docs.

Docker images will begin auto-updating to v1.3.0 in the coming weeks. —

instructions here

.

🔧

The Relay can now use custom DNS servers when registering or validating with the remote API. This makes deployments more reliable in restricted or non-standard DNS environments.

💾

New failover mechanisms have been added to ensure file saving remains reliable across unexpected interruptions or edge cases.

🛡️

Core packages have been updated and security improvements implemented, addressing vulnerabilities identified through Docker Hub scans and dependency audits.

A new version of the Active Directory Sync Tool is now available from the DNSFilter dashboard. This update is recommended for users syncing large on-premises Active Directory environments.

The AD Sync Tool now batches large OU trees into smaller subtrees during sync, solving issues where partial trees appeared due to API timeouts. This ensures the full organizational hierarchy is captured, even in complex AD setups.

The configurator previously displayed only the first 1000 Organizational Units due to a paging limit. Pagination is now implemented correctly, allowing all OUs to be browsed and selected as expected.

A new version of the Windows Roaming Client, v2.1.0 Beta, is now available via the Beta channel. This version can be downloaded from the dashboard , or by selecting the from the in the dashboard.

For more details on Release Channels and the current versions available for both Beta and Production channels, check out our help docs.

You've asked for it, you've got it! With version 2.1.0 Beta, we now have a separate build to support devices that run ARM64-based architecture. This tandem approach ensures that protection can extend to devices outside of the x64 Windows architecture.

We’ve added full to the Windows Roaming Client. This means better compatibility and future-proofing as internet providers and networks increasingly rely on IPv6. DNS queries from IPv6-enabled devices will now route properly through DNSFilter, just like IPv4.

This release introduces a new that monitors and protects the Roaming Client in real time. Here’s what it does for you:

You can think of this as a built-in safety net—if the client goes down, it’ll get itself back up again.

We’ve added a feature to clean up leftover or outdated registry settings automatically when the Roaming Client starts. This helps avoid issues caused by old configurations and keeps the app running clean.

If there's a temporary issue with the DNSFilter API, the Roaming Client will now retry instead of shutting down. This ensures more consistent service.

The client now starts and registers correctly even if there’s a temporary issue reaching DNSFilter’s servers.

A new version of the MacOS Roaming Client is now available via the Production channel.

This version can be downloaded from the dashboard

Auto-update will push out the new release to RCs in the Production Release Channel incrementally over the next week or two. Please refer to our release status page for the latest available versions in both Beta and Production channels.

More information >>

The new 2.x codebase now leverages a system extension and DNS proxy on the endpoint. This enhances security and performance. As noted above, installation of two mobileConfig profiles on the endpoint is a strongly suggested prerequisite as failing to do so will result in the end user receiving two dialog boxes asking for permission to run the extension and proxy.

We fixed an issue where the macOS client wouldn’t retry regular (non-TLS) connections after a secure (TLS) connection failed. This could lead to delays or missed DNS requests. The client now handles retries more reliably to maintain smooth operation.

The macOS extension now correctly re-reads its configuration file and applies fallback settings if some values are missing. This ensures the extension behaves consistently during startup and while running.

We updated the macOS uninstall script to better handle data privacy settings. It now properly reads and filters the necessary configuration details, making the uninstall process cleaner and more accurate.

We've been hard at work making a lot of under the hood improvements to the DNSFilter dashboard and underlying REST API. Since our last update, the following items of note have been completed:

When starting large Roaming Client (RC) cleanup tasks, users will now see a message letting them know it may take time. These jobs run in the background and won’t disrupt other activity.

The Domain Report interface now includes a new “Content Server” choice under “Proposed Category,” offering more precise domain categorization.

Exporting query logs is now more reliable. A new 50,000-line limit has been added, with helpful tooltips explaining how to work with larger datasets. We recommend use of our Data Export functionality to automatically export query logs to your SIEM or S3 bucket of choice.

We’ve streamlined API key management by limiting the number of keys shown to five and removing unnecessary paging.

RC cleanup no longer leaves “All” or “Protected” status counts out of date—they’ll now reflect accurately.

Changes to your user profile will now show up immediately—no need to refresh or navigate away.

Suborg-level uninstall alerts now show “Include Organization Admins” for better clarity. Previous text has been cleaned up.

Cleaned up unnecessary calls to speed up billing page loads.

Permissions now apply correctly when downgrading from super admin to admin.

: You can no longer add sub-orgs to canceled MSP accounts.

Suborg menus now display correctly after being promoted to an MSP.

Filter changes now return you to the first page, and page counts are shown clearly in the RC Management and Query Logs.

Multiple category filters no longer cause issues with the grid layout.

**Query Log Privacy Reinforced:88 When PII Limitation is enabled, you can no longer drill into RC-specific query logs.

Users can no longer skip the final step of saving new recovery codes.

These changes help keep everything running smoothly:

- Improved filtering, validation, and export functions across several pages

A new version of the Active Directory Sync Tool, version 3.6.0 has been released and is available from the DNSFilter dashboard. DNSFilter recommends that users of existing Active Directory Sync Tools perform a manual upgrade to this version when practical.

The "About" section in the AD Sync Tool now displays the refreshed DNSFilter logo along with the current release date for improved clarity and brand consistency.

We improved how the AD Sync Tool handles errors when fetching group users. Previously, certain errors would force the tool to restart the entire sync job, sometimes leaving data incomplete. The tool now recovers more gracefully, allowing the sync process to complete without unnecessary resets.

This release includes several updates to improve compatibility and ensure smoother integration with a wider range of directory environments.

A new version of the MacOS Roaming Client is now available via the Beta channel.

This version can be downloaded from the dashboard

Auto-update will push out the new release to RCs in the Beta Release Channel within the next 24-72 hours. Please refer to our release status page for the latest available versions in both Beta and Production channels.

Existing Beta customers running older MacOS Beta versions should have received an email to advise on prerequisite mobileConfig installation via MDM to avoid spurious dialog box appearances on endpoints.

More information >>

The new 2.x codebase now leverages a system extension and DNS proxy on the endpoint. This enhances security and performance. As noted above, installation of two mobileConfig profiles on the endpoint is a strongly suggested prerequisite as failing to do so will result in the end user receiving two dialog boxes asking for permission to run the extension and proxy.

We fixed an issue where the macOS client wouldn’t retry regular (non-TLS) connections after a secure (TLS) connection failed. This could lead to delays or missed DNS requests. The client now handles retries more reliably to maintain smooth operation.

The macOS extension now correctly re-reads its configuration file and applies fallback settings if some values are missing. This ensures the extension behaves consistently during startup and while running.

We updated the macOS uninstall script to better handle data privacy settings. It now properly reads and filters the necessary configuration details, making the uninstall process cleaner and more accurate.

A new version of the Windows RC is now available via the Production channel. This version can be downloaded from the dashboard Deployments → Roaming Clients → Install Guide, or by selecting the Install Guide from the Control Center in the Roaming Client Management dashboard.

Organizations with Automatic Updates turned on will start receiving this update incrementally from the date of this release.

For more details on Release Channels and the current versions available for both Beta and Production channels, check out our help docs.

Version 2.0.10 represents a cumulative build that incorporates all of the enhancements delivered in the previous 2.0.8 Production version, and the two Beta versions since that was released.

The following enhancements and fixes are being delivered as part and parcel of this release:

The Roaming Client now automatically retries its connection to our service if a temporary error occurs, preventing unnecessary shutdowns. This ensures more stable operation by giving the client multiple chances to validate its identity before taking action.

We’ve streamlined how the Roaming Client checks for updates, reducing redundant status checks that were happening too frequently. This improvement boosts performance and efficiency in the background.

The Roaming Client now includes automatic registry cleanup during startup, improving stability—especially when the system was previously in an unstable or "dirty" network state. This replaces the need for manual PowerShell scripts and ensures a smoother initialization process.

We've resolved a bug that occasionally caused the Roaming Client to go offline unexpectedly, leading to DNS filtering interruptions and VPN disconnections. This fix ensures a more stable and consistent connection, even after the device wakes from sleep.

Devices that previously cycled between online and offline states every 15 seconds when switching between IPv6 and IPv4 networks will now remain connected. Transitions between network types are now seamless and reliable.