Ordering a domain name from OVHcloud is not just about typing an address into a search field and confirming a cart. The choice of extension, initial DNS configuration, and security options determine the long-term reliability of the domain. Here, we detail the technical points to master for registering an OVH domain without unpleasant surprises.
DNSSEC and Zone Signing: What OVHcloud Activates Upon Ordering
A properly secured domain starts with a DNS trust chain. OVHcloud offers the activation of DNSSEC (Domain Name System Security Extensions) directly from the manager, including for domains recently registered by standard customers.
The mechanism relies on DS (Delegation Signer) records published in the parent zone. When DNSSEC is active, the Whois status displays signedDelegation, proof that DNS resolution is authenticated end-to-end. We recommend activating this option as soon as you place your order, as a late activation can cause an uncomfortable propagation period if the zone is already in production.
The procedure on the OVHcloud side is done in a few clicks in the “DNS Zone” tab of the manager. For .fr domains, Afnic automatically checks the consistency of the keys. For classic gTLDs (.com, .net, .org), it is the Verisign or PIR registry that validates. In case of an error in the DS chain, the domain may become temporarily unreachable: it’s better to test with a tool like DNSViz before propagating.
Before starting the procedure, it is useful to order an OVH domain having previously identified the necessary DNS records for your project (MX for emails, CNAME for subdomains, A or AAAA for the web server).
OVHcloud Extensions: .ovh and .cloud Compared to Classic Extensions
OVHcloud is no longer limited to historical extensions. The company now manages over 340,000 new gTLDs, and its proprietary .ovh extension exceeds 83,000 registered domains with notable recent growth. The .cloud extension has seen sustained growth since its inception.
The choice between a classic extension and a niche extension depends on the context:
- The .fr remains the reflex for a site aimed at a French audience. Afnic imposes eligibility conditions (residence in the EU), which limits cybersquatting.
- The .ovh or .cloud can serve as a technical domain (API, staging, internal services) without polluting the main brand identity.
- Geographic (.paris, .bzh) or sectoral extensions (.shop, .tech) offer a thematic signal but are less recognized by the general public.
We observe that new extensions are sometimes offered at a promotional price for the first year, with a significantly higher renewal fee. Checking the renewal price before confirming the order avoids an unpleasant surprise at expiration.
Domain Locking and Protection Against Unauthorized Transfer
The registrar lock (also called clientTransferProhibited) is the first line of defense against fraudulent transfers. At OVHcloud, this locking is enabled by default on most extensions. Disabling it requires an explicit action in the manager, with email confirmation to the owner contact.
This mechanism does not protect against all attacks. A compromised access to the OVHcloud account itself allows the lock to be lifted. Two-factor authentication (2FA) on the manager is therefore a non-negotiable complement. OVHcloud supports standard TOTP applications (Google Authenticator, Authy) and U2F/FIDO2 security keys.
Whois Ownership and Contact Owner
The holder declared in the Whois is the legal owner of the domain. A common mistake is to leave the web service provider or agency as the contact owner. In case of a dispute, it is this field that is authoritative with the registry and UDRP procedures.
When ordering, OVHcloud asks for a owner contact, an administrative contact, and a technical contact. We recommend always placing the end client (individual or legal entity) as the owner, even if a third party manages the technical part.
Initial DNS Configuration After Ordering from OVHcloud
Once the domain is registered, OVHcloud automatically creates a DNS zone hosted on its servers (dns*.ovh.net). This zone contains default records that point to an OVH parking page.
Three priority actions to take in the first minutes:
- Create or modify the A record (and AAAA for IPv6) to point to your server or web hosting IP address.
- Configure the MX records if you are using email (OVHcloud includes a mail offer with certain hosting plans).
- Add an SPF record and a DKIM record for email deliverability, especially if you are using a third-party service like Microsoft 365 or Google Workspace.
The default TTL (Time To Live) at OVHcloud is generally set to 3600 seconds. Lowering the TTL to 300 seconds before a migration allows for a quick switch in case of problems, then raising it once the configuration is stabilized.
OVHcloud API for Bulk Management
Administrators managing several dozen domains benefit from using the OVHcloud REST API. The official documentation describes a structured workflow: creating a cart, adding the domain, configuring options (DNS, transfer, Whois), then validating the order form. This process is fully scriptable, allowing for the automation of recurring orders or defensive registrations across multiple extensions simultaneously.
Automatic renewal can be set domain by domain from the manager. A domain not renewed enters a grace period, then a redemption period (high recovery cost), before permanent deletion. Setting up automatic renewal with a valid payment method remains the most reliable way to avoid losing a critical domain.
