I can just imagine that moving to IPv6 is as messy on Azure than it is on AWS.
Don’t get me wrong, actually using it is simpler, you can just have your range and then be free to do whatever you want. But the fact that it was added later to a stack never made for it shows everywhere, which makes UX tough.
Currently struggling with metadata service weirdness and slowness in IPv6 land on AWS :’)
Don’t get me wrong, actually using it is simpler, you can just have your range and then be free to do whatever you want. But the fact that it was added later to a stack never made for it shows everywhere, which makes UX tough.
Currently struggling with metadata service weirdness and slowness in IPv6 land on AWS :’)