I reached out to support, same response, we deployed a new site with IPV6 dual-stacked without DNS filter, FortiDNS seems to be working fine with V6 via the UTM, but it sucks we still dont have this on the roaming clients
Dirk Van den Abbeele
I am comparing several companies with dns filtering as a core business. Most of them support ipv6. This could become a dealbreaker for me (and probably also for others).
When is a real IPv6 resolver coming? I am working to transition my networks to primarily IPv6, which I can’t do with DNSFilter!
This issue was open for 5 years, kinda ridiculous. I've since switched to controld.com as they seem to be working off dnsfilter feature request portal, and adding the features. ControlD didn't exist 1.5 years ago, and launched with full IPv6, DOH, and DOT support.
Thank you everyone for your patience. To update you, we have implemented IPv6 support for the Windows Roaming Client. We've been testing and starting next week we would like to invite individuals to help us test the Win RC on a few select test devices in your environment. If you're interested, please email email@example.com with IPv6 in the subject line. Thanks!
Steve: Steve, thanks for your reply. BUT we need an IPv6 Resolver Adresse and not a Windows Roaming Client. More and more providers are moving from IPv4 to IPv6. We have to configure an IPv6 Resolver in the network settings on the routers (as Fritzbox as an example).
Steve: Just to re-iterate on what Thomas said, an IPv6 Resolver would really push things forward a lot more with most of my networks as I'd finally start being able to implement IPv6 properly on those networks and still provide protections with DNSFilter. The Roaming clients can come after for me.
Thomas: Appreciate the feedback. Quick question for you, our engineers think this is pretty straightforward by supporting a 64-bit prefix. Would that work for your use case?
Steve: Good evening Steve
Thanks for asking - I'm not an IPv6 specialist, but as far as I understand, a DNS server in the router cannot be configured as a 64-bit prefix. The 64-bit prefix only indicates part of the network address, not the destination address of the DNS server.
I'm surprised that it's so difficult to make DNSFilter's DNS servers accessible via IPv6 (IPv6 DNS resolver). Today, DNSFilter only offers an IPv4 resolution. CISCO Umbrella already offers IPv6 addresses - see https://support.umbrella.com/hc/en-us/articles/230563727-Does-Umbrella-Support-IPv6-.
Should it be helpful, I am available for a meeting via Zoom / Teams.
Thomas: I think what Steve is suggesting might be surrounding how DNS Filter identifies which policy/site to associate your request with. Much like competitors, you put your /64 prefix into their config and when a request comes from that range you have the settings applied as appropriate.
If that is the case, then yes, that would be enough if you could also add multiples like you can with IPv4.
I'd love to see an IPv6 resolver sooner rather than later.
Please implement IPv6 asap. Thank you.
Ken, can you inform us about current state of the integration?
5 months later and it still seems to be zero progress on this very important issue.
Many many companies/people have been waiting for over a year and yet there is zero updates coming from the support group.
This needs to be implemented and implemented now.
I really fail to see why this is taking so long
We are moving to an Azure AD only environment, but we can't use IPv6, until DNSFilter supports IPv6. This is fundamental!
Using the iPhone DNSFilter app on Telstra within Australia doesnt work as Telstra is using ipv6 for their DNS servers and im being told the app wont work when on 4G because of Telstra using ipv6 for their dns server