Good afternoon, dear!

I suffer a question: is, say, I have a website, and there is a desire to make it available on IPv6. So, it is more correct (more precisely, more convenient for users) to bind an AAAA record to the same domain name as it does for IPv4, or will it have another name, just for access via IPv6?

Example: we have a website www.lazurit.com , available only on IPv4. To please visitors, what to do:

  1. simply register its IPv6 address in addition to the IPv4 address to the name www .lazurit.com, or
  2. We get some name w6 .lazurit.com for IPv6 access, and at www ... do we leave only IPv4 access?

The question is not idle, so far as I can see, everything is cloudless with IPv6 support, and in some places, although the support is stated, access via this protocol is actually buggy or very slow. T.ch. Option 1 seems to cause problems, even if the site is not opened for a specific visitor. Option 2, it turns out, is only for technomaniacs, because a simple visitor is unlikely to think about such trifles ...

Advise what to do?

  • And what a demon is worth? For example: like nginx can be proxied with any conditions. For example, there is also support to determine. For users, it will be implicit. A technomaniac with a tuned ipv6 just there and will fall. - org
  • So proxy or not, and what name should a demon respond to? - A.J.
  • Name one will be. inside proksiruesh. - org
  • Those. The answer to my question is to do the same name for both IPv4 and IPv6? - A_C


1 answer 1

I would go in two steps:

  1. First, your first option, ipv6.example.com with A + AAAA, www.example.com with A-record only. If there is a community on the site, it is announced, volunteer activists go, check, report (you need a convenient report form in two buttons “working / not working” and optional comments).

    If the option with volunteer testers is not suitable for any reason - another possible alternative is to hang an “invisible” iframe on www.example.com on some A + AAAA ipv6test.example.com and study how it works in the logs the percentage of users is "lost". Again, there are a lot of things you can think of to hide problems - for example, by javascript, you can remove the “hung” iframe by timeout, so that if everything does not work, it does not make the browser hang in the “load” state and do not confuse users for more than a few seconds.

  2. Then, when it will be seen how many problems got out and how to solve them - to do it right, one example.com (with optional www. - as you consider canonical) with A and AAAA records. Actually, in theory, it is right that way, but since you have doubts about whether it will not create problems, you should take it in advance and check it out. You can test the behavior of browsers on yourself by displaying your own iframe to some intentionally not responding to anything (i.e., no TCP RST or ICMP port unreachable) broken.example.com.

Why is the first option suitable only for temporary tests? Because no one will walk for a long time at this address, and all of its suitability is only for temporary testing.