[marks]

hi SrvGuy

yes, you're right, whenever there is an issue with IPv6 (or anything else) it should be reported right away. The best way is through our Incident Ticket system (for now, in the old customer interface) so our engineers can check it right away. And don't forget to attach logs to it!

Same with the routing. Any general issue or maintenance will be reported here: status.ovh.net, but if there are individual issues, do reported them ASAP to our engineers.

Let us know if you need more help.

[SrvGuy]

Also lately OVH IPv6 connectivity has been ridiculous there has been serious problems with Cloud and Classic series. And I'm not now talking about a few hours, I'm talking more like days of intermittent connectivity. Routing is also totally (ahem) for some destinations.

[SrvGuy]

Just as additional remark. Windows servers do not have IPv6 preconfigured, so it needs to be manually configured for each server separately. Duh!

[SrvGuy]

I've noticed that with multiple service providers. If there's an IPv6 issue, it can take DAYS to get fixed? Why? Well, they're not monitoring their IPv6 traffic properly and nobody's complaining immediately if it doesn't work. So it can take a while before issues get fixed. I've had similar experiences now with three completely independent service providers.

[alvaroag]

Never noticed that before, but yes, there's a bug in that, and that also applies to dedicated servers. There's currently nothing to do about that, cause I don't think they will make necesary changes quickly. But, hopefully, someone from OVH staff will read this, and send it as a suggestion or as a bug, so at some time they will consider adding IPv6 records for the VPS and dedicated NS names. You can also write to support@ovh.co.uk to ensure they receive your comment.

I think this is probably due to the slow implementation of IPv6 around the world. Because of that, most of the users still worry only about IPv4, not IPv6. I bet most OVH users are not yet using IPv6, sometimes because they don't have it with their local ISPs, other times because they do not matter about it, "'cause everyone still haves IPv4".

Currently, your faster & easier solution would be to buy a cheap domain, either at OVH or any other registrar. Just as information, I bought a .ovh last week for €1 + VAT. Not sure if it's the cheaper, but may me really near to that.

[SrvGuy]

OVH does assign name vpsXXXX.ovh.net for server, but why doesn't that name have bindings to IPv6. AAAA record is missing as well as reverse for the IPv6 address? Could this be fixed? Now I have to maintain my own domain, configure AAAA records and set revers when I would be completely happy with CNAME if the IPv6 part would be properly configured.

- Thanks