In this article

Version 2.1.0 of the DNSFilter Windows Roaming Client introduces major service improvements and expanded protocol support designed to enhance reliability and flexibility.

Summary of Benefits

• Improved service resilience with automated monitoring and restart
• Flexible configuration through appsettings.json
• Enhanced IPv6 support for modern network environments
• Transparent failover between IPv6 and IPv4 to maintain continuous connectivity
• Native ARM64 build for optimized performance on ARM64 Windows devices

Automated monitoring and agent restart 

Starting with version 2.1.0, the Roaming Client now installs two Windows services: the agent and a Service Manager.

The Service Manager continuously monitors the agent service to ensure uptime and stability.

Key Service Manager Functions:

• Checks the agent service status every 5 seconds

• Automatically restarts the Roaming Client service if it stops or encounters an issue

• Allows a 30-second grace period before restarting to accommodate intentional service restarts

• Provides a 300-second (5-minute) boot grace period to support normal system startup processes

✍️ Modify these timing values in the appsettings.json file, located in the Service Manager directory:

• DNSFilterAgent\Service Manager

• DNSAgent\Service Manager

🚨 Important: Because this latest agent version introduces two Windows services, it is necessary to stop the agent and Service Manager in order to stop the Roaming Client service for more than 30 seconds. If the Service Manager remains active, it will automatically restart the agent service.

Log Folder Structure

With the Service Manager introduction, the log folder now includes:

• 1–10 agent-operation logs (up to 20 MB each)

• 1–5 dns-query logs (up to 10 MB each)

• 1–5 service-manager logs (up to 10 MB each)

The total log folder size can reach up to 300 MB.

IPv6 support enabled by default

Version 2.1.0 also activates IPv6 support in the default operating mode: IPv6-IPv4.

With this default configuration:

• IPv6 is the preferred protocol when available

  • If IPv6 is unavailable or unsupported, the client automatically falls back to IPv4 mode

  • When IPv6 becomes available again, the client switches back to IPv6 mode without requiring manual intervention

• The Roaming Client listens on IPv6 and sets the system’s DNS servers as:

  • IPv6: ::1

  • IPv4: 127.0.0.0

The client automatically prefers IPv6 when available and falls back to IPv4 if needed. This switching happens seamlessly to ensure uninterrupted service.

On networks with limited or no IPv6 support, the client will operate entirely over IPv4. Manual switching between IPv6 and IPv4 is not required, as the client handles this dynamically based on network availability.

ARM64 Build of the Roaming Client

Starting with the 2.1.0 release, the Roaming Client is available in both x64 (existing) and ARM64 native (new) build formats.

The ARM64 build is designed for devices running ARM64 versions of Windows, providing a native experience without relying on the x64 emulator. This ensures better performance and compatibility on supported hardware.

Select the ARM64 PKG download link from the Install Guide if operating in this build.