zajDee

True dat. Some of the mishaps can be attributed to incompetence and some to lack of desire to be real ISPs for the future. Too bad one is usually geographically restricted to one or a very few ISPs, especially when all of them are doing IPv6 wrong.

Forgot to mention that while O2 provides you with a poor single /64, UVTnet gives you a nice and shiny /48 (others currently stick to /56s). What a difference.

If this is DSL/FTTH, don't wait and switch to T-Mobile, Metronet or UVTnet. O2 have been doing this wrong since 2012 and it doesn't look like they will fix it in this decade.

pref64 is the generic term for a "NAT64 prefix".

The pull request helps advertise the NAT64 prefix via router advertisements (while DNS64 uses, well, DNS to advertise it).

The DNSSEC problem is known and has a solution: any stub resolver performing DNSSEC validation should also perform the DNS64 synthesis, should the network be running DNS64/NAT64. The support of DNS64 in stub resolvers is almost nonexistent though (as is the existence of DNSSEC-validating stub resolvers).