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 7 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(1)
最终结果应该是在 IPv4 和 IPv6 的相同主机名上运行站点。仅以单独的名称提供 IPv6 将使未来仅使用 IPv6 的用户无法访问该站点。他们不会显式键入 ipv6.example.com 来访问该站点的 IPv6 版本,并且该站点的所有链接都将指向 www.example.com,而不是 ipv6.example.com。对于 IPv4 连接性较差(运营商级 NAT/NAT444)而 IPv6 连接性良好的用户来说也是如此。他们将无法从 IPv6 中受益。
使用单独的主机名测试 IPv6 设置是可以的,但仅用于测试。
如果提供 Web 服务器连接的 ISP 提供 IPv6 连接,那么它应该与 IPv4 连接一样好、一样快。如果不是,他们就没有正确完成自己的工作;-)
是的:我在一个主机名上同时使用 IPv4 和 IPv6 运行我的所有网站 :-)
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 :-)