In this article

Use this article to understand IPv4 and IPv6 compatibility with local domains and resolvers configured in the DNSFilter dashboard.

DNSFilter is actively developing full IPv6 support for local domains and resolvers used with Roaming Clients. Until that update is available, use default IPv4 settings to ensure compatibility. Follow the DNSFilter Changelog for beta and production release announcements.

IP mode capabilities

The charts below outline current IPv4 and IPv6 support for local domains and resolvers.

✅ Supported. The Roaming Client agent uses the configured IPv6 resolvers as expected.

⚠️ Limited support. The Roaming Client agent uses supported IP addresses. Other addresses may not function correctly.

⛔️ Not supported. Configuring local resolvers in this way may produce unexpected results when accessing local domains.

Windows Roaming Client

Transparent Proxy Connection Mode

When Transparent Proxy Connection Mode is active—with or without PreCheck—IPv6 is fully supported. Queries respect the address family of the original request rather than being forced over IPv4 or IPv6. This maximizes compatibility with all applications, respects Windows and Group Policy settings (such as interface metrics), and reduces potential networking issues.

If Transparent Proxy intercepts a DNS request over IPv4, the query is sent upstream via IPv4—either to its original destination (PreCheck enabled) or to DNSFilter resolvers (PreCheck disabled). Requests intercepted over IPv6 are sent upstream via IPv6.

Loopback Connection Mode

IP mode settings differ depending on the Connection Mode in use. Loopback Connection Mode (Classic DNS Filtering) requires modifications to update the default IPv4 setting. Edit the applicable file based on the agent version in use:

• Windows agent v3.x and higher. Configure settings in appsettings.Overrides.json
• Windows agent v2.x and lower. Configure settings in the Windows registry

macOS Roaming Client

Mobile Roaming Clients