Feature request: DNS64 option
Use case: I'm on an IPv6-only network that optionally provides outgoing IPv4 support through use of NAT64. There is no automatic route for that, but internal resolvers use DNS64 to map address accordingly.
Problem: But now I want to use NextDNS, and of course even if I only connect to IPv6 endpoints of NextDNS, I will still get answers with IPv4 addresses which my device cannot connect to successfully because there's no route.
Idea: In my profile settings, if there was an option to enable DNS64, then the problem would be solved. By default the prefix 64:ff9b::/96 should be used, but it would be even better if also a custom internal prefix could be configured. We use our own custom subnet for DNS64.
Additional resources: The Google Public DNS also provides such a service, see https://developers.google.com/speed/public-dns/docs/dns64 -- however they only support the default prefix and not something custom.
+1 for this request.
I have been using NextDNS for a little over a year on my mobile Android phone (and other devices on my home LAN, but they are not impacted by the issue mentioned here), as a private DNS, with much pleasure. But since I changed my mobile operator I can't do it anymore.
I changed my mobile operator twice in the past month and both new carriers break NextDNS. I thought at first it was some kind of censuring. But I realized my device was using IPv6 only and that may be the related to the issue. After some troubleshooting from my phone with "dig" and a few IPv4 and IPv6 DNS servers, I figured that the issue was only happening if I set an IPv4 server as a DNS server, while forcing a IPv6 server was not causing any issue. The thing is there is no way I can tell about globally forcing IPv6 on an Android device when I use the mobile carrier. And even if there was, I don't feel like manually switching IPv4 to IPv6 and vice versa when moving from mobile carrier to home/any wifi network.
I believe this is more than a feature request. The two "new carriers" I mentioned above are two of the 3 biggest players in France (Orange/Sosh and Bouygues Telecom/B&You). And I'm pretty sure many other provider in the world use this kind of DNS64/NAT64 feature. Which means that the current state means NextDNS is missing a lot of business opportunity.
I have exactly the same problem. When I'm on 5G at Bouygues (IPV6), I often get the error message ERR_NAME_NOT_RESOLVED, for example if I want to go to my.nextdns.io, route calculation on waze doesn't work, etc. On Bouygues WIFI (IPV4) no problem.
Folks, Just switching over to ControlD [.com] who has about 100% of the requested features, including DNS64
- 11 days agoLast active