If you have the August 13, 2024—KB5041580 update. You’re good.
Old tale, I know, but just cause v4 is running out on the internet it doesn’t stop anyone from using it in their homes. I manage some ASNs on the internet. I have no need yet to worry about implementing v6 on the inside.
The thing is that if IPv6 were actually adopted, it would be straight up better. For everyone. It’s easier to use if it’s all the networking instead of just a niche case.
It’s really not though. ISPs are a problem, but every hosting provider I’ve used has offered IPv6. It’s really trivial to setup IPv6 name DNS, and host a website on both IPv4 and IPv6. I just do it by default now.
Once it becomes the default to deploy to both, if IPv4 died then the IPv6 side would just keep working.
For DNS, you can make a single glue record contain an IPv4 and IPv6 address.
DNS just needs A and AAAA records for the Name servers. NS records still point to the hostname as normal.
For Web servers, the web server just needs to bind to the IPv6 address(es). Then in DNS just have an A and AAAA record for each website hostname. The server name directives will cover both.
There really isn’t much to it right now. The technology is mature now. It used to be a pain, but now it isn’t.
