@Martineau I am finding many issues with the new IPv6 defaults, specifically this one.
Code:
#module-config: "validator iterator"
module-config: "dns64 validator iterator" # v1.01 perform a query against AAAA record exists
dns64-prefix: 64:FF9B::/96
The issues are not just a slower connecting OpenVPN connection because it is trying IPv6 addresses first as previously posted above. At least the OpenVPN connection eventually goes live and usable.
Here is what I have seen so far:
- Outlook, Spotify, OneDrive, Dropbox, Skype, and many other such services either do not load at all or load even slower than the OpenVPN client example above (sometimes half an hour and still not connected).
- The 'Your Phone' program in Windows 10 doesn't connect at all, even with a computer left on overnight.
- The 'Fitbit' connections fail from watch to phone (Android) app. The watch cannot connect at all.
I would like to suggest that the 'dns64-prefix: 64:FF9B::/96' option be selectable in the 'i' command instead of being automatically applied if that makes sense of course.
Other than this ('almost' showstopper), the v2.05 Unbound_manager release seems to be working well.
Thanks again.
Edit: This is kind of funny. Another issue is that websites will randomly switch language with the 'dns64-prefix: 64:FF9B::/96' option set, while browsing from one link to another within the same site. Funny at first. Gets old real fast.