Sjoerd Goes
Hi,
Is Ipv4 / Ipv6 Dual Stack DNS on the roadmap as well?
Minetta Gould
Sjoerd Goes: Thanks for the question! Just to make sure we’re talking about the same thing: are you asking about IPv6/IPv4 mode support for the Roaming Clients, or something broader like the Relay, Sites, or resolvers?
Right below your comment you’ll see that Windows RC v2.2.1 already includes configurable IPv4/IPv6 support, and macOS RC v2.4.X (coming in Q4 2025) will bring the same. Just want to be sure we’re chasing the right flavor of dual stack here. 😉
Kate Trojanowski
Windows released configurable support for IPv6/IPv6-IPv4 with Windows RC 2.2.1 https://dnsfilter.canny.io/changelog/8-13-august-13-windows-roaming-client-v221-production
macOS will include configurable support with macOS RC 2.4.X, which is slated for Q4 2025. This has already been tested and in the release pipeline for a larger build.
In addition to the configured option support for IPv6 and IPv6-IPv4 mode for Windows and macOS RCs, we are also working on integrating the DNS Pre-Check technology from our Zorus acquisition into the Windows Agent. This is also In Progress, and expected to go to Beta in early Q4.
DNS Pre-Check is a transparent DNS proxy that will be built into the Windows Agent. It validates and filters DNS queries locally on the device before they leave the network stack, eliminating the need to modify DNS settings or configure local domain, Upstream IP, etc.
This approach ensures filtering works consistently across any network—even untrusted environments such as hotels, public Wi-Fi, or shared corporate LANs—while maintaining reliable connectivity and avoiding conflicts with other software.
Minetta Gould
now
C
Carl Levine
beta / early access
The current Windows RC 2.1.0 Beta has IPv6-IPv4 mode enabled by default. In concert with the new Service Manager functionality, network switching is seamless and quick. Give it a try, and let us know what you think. For the MacOS RC requestors, this is coming up soon.
Mark Porter
Carl Levine When do you expect IPv6 support for the macOS RC? I heard from support we should disable IPv6 as part of our troubleshooting and I'm interested to know when you fully expect to support it and if there's anything we need to do manually to implement it once it hits prod.
Jarrod
Is IPv6 support GA in 1.15.3? If so, does it still require a registry change?
C
Carl Levine
Jarrod: Still requires a registry change. UpstreamIpVersion registry key can be changed in HKLM\Software\DNSFilterAgent\Agent to prioritize it. The default is empty on UpstreamIpVersion, which defaults the agent to IPv4. To set IPv6 as default, put the following value into the field for this key:
ipv6 / ipv6-ipv4 / ipv4
This will prioritize IPv6, then fall back to an auto-detect, and finally IPv4.
Thomas J Sweet
Carl Levine How about on iOS?
Sam Rankl
Guys, this is starting to cause more issues for us. Comcast and others are moving to IPv6. We can't have our employees having to disable DNSFilter roaming client when working remote. This feature has been showing as "Live in 90 days" for months now. A little more clarity would be good. We had access to the beta IPv6 client sometime ago, and can no longer download it. Is there a new IPv6 beta client we can test and report back on?
C
Carl Levine
Sam Rankl: Your request was certainly timely. We just pushed v1.15.2 Beta of the Windows Roaming Client about 30 minutes ago. While IPv6 is not turned on by default, the UpstreamIpVersion registry key can be changed in HKLM\Software\DNSFilterAgent\Agent to prioritize it. This version fixes a number of issues that were present in prior iterations of the Windows RC specific to this function, and those details are available in the release notes (https://dnsfilter.canny.io/changelog/11-27-november-27-windows-roaming-client-1152-beta). We welcome your honest and candid feedback on this functionality in this beta version.
B
Brendon Haughey
Carl Levine: What value do we need to set the UpstreamIpVersion key to in order to prioritize IPv6?
C
Carl Levine
Brendon Haughey: The default is empty on UpstreamIpVersion, which defaults the agent to IPv4. To set IPv6 as default, put the following value into the field for this key:
ipv6 / ipv6-ipv4 / ipv4
This will prioritize IPv6, then fall back to an auto-detect, and finally IPv4.
Bogdan Pavel
Is this something the DNSFilter team can implement, or is it not feasible and we need to find/move to other products ?
B
Brendon Haughey
Can we get an update on this please. It's bizarre that this request has been open for 6 years with no end in sight.
C
Christopher Burrell
Need v6 support for Roaming clients on all endpoints
Load More
→