ingber wrote:
Or, am I missing the way a webserver with IP4 and IP6 should be used?
You've pretty much got it, with the one clarification that you are adding AAAA records for your IPv6 address, not A records (which only hold IPv4 addresses). You can do this in the advanced DNS manager within the Network Solutions interface.
Also, one thing to be slightly cautious of - in general, IPv6 devices are supposed to prefer IPv6 addresses when both are available in DNS. However, there is a chance that some client devices may prefer the IPv6 address even if they don't really have a functional end-to-end IPv6 path to your server, which could then entail (potentially lengthy) timeouts before they fall back to IPv4.
What complicates this failure mode is it's not really something you can detect from the server side, unless some of your clients complain. Nor may they even understand why things are delayed, so on their part they may just assume it's the network.
In some cases, in the near term services are choosing to publish slightly different addresses (e.g., "www6" or using a ".v6.xxx.com" subdomain) for users who know they wish to use IPv6.
This should become a decreasing issue over time, and it's one of the things, among others, that IPv6 day in June is hoping to shed more light on. But in the near term, it's something to be cognizant of.
-- David