Mark Elvers

@reynir Yes, I found that test all the options using these four commands (on a dual-stack machine) ``` curl --resolve opam.ocaml.org:443:[2001:bc8:1d80:4a00::1] -o /dev/null https://opam.ocaml.org curl --resolve opam.ocaml.org:443:[2001:bc8:5080:a405::1] -o /dev/null https://opam.ocaml.org...

@avsm I have written an OCurrent pipeline that resolves the name, validates the certificates, tries to download from the website, and then posts the results to a Slack channel. http://observer.ocamllabs.io...

@avsm The IPv6 address of `staging.ocaml.org` should be `2001:bc8:1204:a40b::1` rather than `2001:bc8:1202:920c::1`. Please could you update the DNS entry?

We also update the images via OCurrent Deployer using `docker service update --image`, which only works for a service, not a Docker Compose. As we only have a single host...

Similar issues can be seen on GitHub: https://github.com/moby/moby/issues/24379, https://github.com/moby/moby/issues/24847, https://github.com/moby/moby/issues/43643,

For my application, [sqlite3-backup](https://github.com/mtelvers/sqlite3-backup), either version works. Is there something in your use case which is different to mine?

Thanks @pirbo and @klakplok. I have updated the PR with these changes.

Thank you for your comment. v3b.ocaml.org, v3.ocaml.org, ocaml.org and www.ocaml.org are all the same machine. Are you proposing an HTTP 301 redirect on v3/v3b rather than the current DNS based...

As the redirection is currently in place using DNS, I think no further action is required. Please reopen the issue if anything further is required.

Thank you. The second part is to create `staging.docs-data.ocaml.org` as a CNAME pointing to `staging.docs.ci.ocaml.org` (or as an A record with the IP 51.158.234.115) Both staging and live have two...