As a interesting test; I temporarily ran a public wireless network with only IPv6 connectivity for a short while. Now I couldn't really find a lot of information online about best practices for this. Therefore I turned off my DHCP for the subnet and continued to perform route advertisements with 'RDNSS' added in for this subnet. This was set to point at my local caching resolver on its V6 address.
I then connected several Android phones, several iPhones, a computer running Windows 10 and my laptop running Ubuntu 20.04 to it. All of these just worked except for Ubuntu however it soon became painfully obvious just how little works via IPv6 at present. Big stuff was no problem; so Microsoft; Google; owned service etc but even stuff like the BBC is very much v4 only at present. I had a poke around and it seems like 464xlat appears to be a well supported (on mobile devices) and less troublesome transition mechanism (say vs DNS64) however I could find little information as to whether compute type devices support this widely yet and if so how to advertise the functionality on your network to allow compatible devices to automagically configure themselves. Any pointers would be appreciated! Till then I continue to roll out dual stack to my clients with excellent results on the BT network. I also make no apologies to BT for being 'that person' who was the first to ring in when they broke all of the early allocations during some maintenance last year!
