I had an internal OVH bug corrected on .fr domains

Written by

in

I recently discovered a new problem at OVH: anyone who had registered a .fr domain name with OVH was affected by a new limitation.

Here's the story of a 2-week journey that, for once, ended in success.

Article from this post LinkedIn.

The problem

Technically ▶️ OVH blocked the change of DNS servers if all the NS present in the destination DNS zone were not defined.

In practice ▶️ This prevented flexible and efficient management for hosts like me.

Vulgarisation ▶️ OVH thought it was god. 😅😅

The impact was dramatic for the freedom of the French Internet... 🥐

What to do about it ❓

I started by opening a ticket at OVH.

Those familiar with OVH won't be surprised to learn that it was a waste of time: after an off-the-cuff response, then a call and a few exchanges, the final answer was that there was no way to override this limitation. 😰😰

OVH even silently closed my ticket after I told them that they were the support that least bothered to solve the real problems I had. It certainly wasn't a very nice comment, but it was true and was intended to make people react in the direction of solving the problem and not closing the ticket. 😅

My reaction ❓

▶️ First of all, I transferred my .fr domains to HaiSoft, a trusted registrar with excellent support and Afnic accreditation. Transferring a domain is very simple.

▶️ Then, as a «little guy», getting a behemoth like OVH to move is no easy task... So I used my brain! 🤯
💡 If OVH doesn't listen to me, it'll probably listen to the authority responsible for .fr domains!

So I contacted Afnic.
And that's where the story begins! 🍿🍿

I was lucky enough to be looked after by David Chansard, whose commitment is no longer in question. 💪
You can read his post here to find out more about his investment in the French Internet.

🕒🕝🕜🕐
So David patiently contacted OVH and kept me informed of the rollercoaster ride: one minute the problem was fixed, the next I had to re-open a ticket... His follow-up was exemplary despite these difficulties.

👉 In the end, OVH announced that it was correcting the problem last Friday (a strange day for a production launch).

And on Monday 1 July, I was able to confirm this thanks to a test carried out by one of my valued customers Mathieu Cellucci (Labographic) whom I thank, that it was indeed well resolved! 🍾🥂

Conclusion ▶️ When you're small, you can make things happen if you're clever and you meet the right people.

Never give up, you can make things better! 💪

Thanks again to Afnic, David Chansard and Mathieu Cellucci, without whom this would not have been possible. The world is a better place thanks to you.

To choose the best WordPress hosting from a host that is committed to your comfort and freedom, click here. click here.

Comments

2 responses to “J’ai fait corriger un bug interne d’OVH sur les domaines .fr”

  1. Pierre avatar

    Hello Robin, can you tell us more about the technical problem?

    Well done for getting things moving.

    Pierre
    P.S.: when I open a ticket I ping @olesovhcom on Twitter right after and I get a quick reply. :-)

    1. Robin Labadie (LRob) avatar

      Hello Pierre,
      On a technical level, there's not much more to explain than: «OVH blocked the change of DNS servers if you didn't define all the NS present in the destination DNS zone.»
      In my configuration, I have customers define the 3 LRob DNS slaves, so that they can be migrated to new machines over the years without interruption and without them having to make the slightest change on the registrar side.
      The block in question meant that the DNS master also had to be defined, breaking all this logic... In my opinion, this was an insane limitation, and clearly abnormal according to AFNIC, which dealt with the matter in all seriousness.

      PS: For my part, I've cancelled all my services with OVH and I'm choosing service providers who respond without fail. This has drastically improved my quality of life!

Leave a Reply