Best practice to support IPv6 for already running site? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.

Closed 5 years ago.

I开发者_StackOverflow中文版mprove this question

Recently a friend of mine moved his site to new hosting, and it was Linode (at Newark), which offered IPv6 as well as IPv4.

As we all know the latest fashion is to support IPv6, so he enabled it on server and added corresponding AAAA-records, and then we both got a discussion on whether IPv6 site should be "tied" to the same hostname (URL) as IPv4 one.

Simple to say, should the site be available under www.domain.tld both via IPv4 and IPv6, or there should better be different subdomain for IPv6 (like use www.domain.tld for IPv4 and something like ipv6.domain.tld for IPv6 version)?

If you ask me, I'd like to see both version under the same name, plus it weaves the risk of Google ban one version for "copy content from another site". But then, I also believe that IPv6 not always run as fast as IPv4 (so far), so establish different names may help.

What you say? What would you do if it was your site? And are there any best-practice guides of how to implement IPv6 on sites?

Thank you in advance! This is my first question I ask here so home I won't break the rules, but I can't find much info on subject.

---

The end result should be to run the site on the same hostname for both IPv4 and IPv6. Offering IPv6 only under a separate name will make the site unreachable for future IPv6-only users. They will not explicitly type ipv6.example.com to reach the IPv6 version of the site, and all links to the site will point to www.example.com, not ipv6.example.com. The same goes for people that have bad (Carrier Grade NAT/NAT444) IPv4 connectivity and good IPv6 connectivity. They won't be able to benefit from IPv6.

Testing the IPv6 setup with a separate hostname is ok, but just for testing.

If the ISP that provides the connection to the web server offers IPv6 connectivity it should be as good and as fast as the IPv4 connectivity. If it is not they are not doing their job properly ;-)

And yes: I run all my websites with both IPv4 and IPv6 on one hostname :-)