ovh-net

Lede: Point an OVHcloud-registered domain at Webflow hosting with three DNS records, and keep the mailboxes and servers you already run inside OVHcloud's European datacenters.

Webflow hosting covers SSL provisioning and CDN delivery. It doesn't run your mailboxes, and it doesn't take over a DNS zone held at an outside registrar. Teams whose domain and email live elsewhere need all of that to keep working while the site itself moves to Webflow. European organisations usually carry a second requirement on top: mail and database records have to stay inside EU datacenters.

Splitting the work along those lines is straightforward. OVHcloud keeps the registrar and DNS duties, mail routing included, while Webflow serves the site with SSL and content delivery. Three records in the OVHcloud Control Panel point the domain at Webflow. For anything deeper, such as scripted record changes across many domains or content sync from a backend, the Webflow Data API and the OVHcloud API do the work.

This pairing fits agencies holding client domains at OVHcloud and European businesses whose mailboxes sit in France. Developers running services on an OVHcloud VPS or Public Cloud instance can point a subdomain at that backend from the same zone. Compliance-driven teams in finance or healthcare get to keep data in EU datacenters while the marketing site runs on Webflow.

How to integrate OVHcloud with Webflow

What is OVHcloud? OVHcloud is a French European cloud provider that runs more than 46 datacenters on 4 continents. It registers domain names and manages DNS zones. It hosts mailboxes through Email Pro and Hosted Exchange, with the data stored in France. Its infrastructure catalog covers VPS, dedicated servers, and OpenStack-based Public Cloud, including S3-compatible Object Storage and managed databases.

Teams reach for this combination when the domain, the mailboxes, or a backend already lives at OVHcloud and the site is moving to Webflow. No OVHcloud app exists in the Webflow Marketplace, so the connection happens in DNS and in each platform's API. DNS configuration in the OVHcloud Control Panel points the domain at Webflow hosting without any code. Code Embed elements place OVHcloud Video Center players on Webflow pages. The Webflow and OVHcloud APIs cover scripted DNS changes, CMS sync, and publish-triggered work on OVHcloud servers. Most setups start and end with DNS, and reach for API work only when there are many domains to repoint or a backend to connect.

Connect your OVHcloud domain to Webflow with DNS records

Pointing an OVHcloud domain at a Webflow site takes three DNS records and no code. One thing trips people up more than anything else here: OVHcloud's Webflow guide still publishes the retired pre-Cloudflare values, listing 75.2.70.75 and 99.83.190.102 as two A records and proxy-ssl.webflow.com. as the CNAME target. We stopped accepting publishes to those records on January 13, 2026, and began switching off the legacy hosting behind them on June 1, 2026, as the DNS migration guide sets out. Copy the values from your own Site settings, never from a registrar tutorial.

Point the domain at Webflow hosting

The work spans two dashboards, Webflow first and then the OVHcloud Control Panel. OVHcloud labels its form differently from most US registrars: no Host field, no Points to field. You click Add an entry, then fill in Sub-domain and Target.

To connect the domain:

1. In Webflow, go to Site settings > Publishing > Production, click Add a custom domain, then choose Manually add domain. Copy the records shown there, including the one-time verification code.
2. In the OVHcloud Control Panel, go to Web Cloud > DNS zones and select your domain name.
3. Click Add an entry, choose A, leave Sub-domain empty for the root domain, and set Target to 198.202.211.1. Click Next, then Confirm. OVHcloud's A record guide walks through the same form.
4. Add or edit the CNAME entry with Sub-domain www, then set Target to cdn.webflow.com. including the trailing dot, which is how OVHcloud writes CNAME targets throughout its own guides.
5. Add a TXT entry with Sub-domain _webflow and the one-time-verification= value from Site settings.
6. Delete every AAAA record on the root domain and on www, and remove any leftover A record on www, so nothing conflicts with the new entries.
7. Back in Site settings, click Verify domain, then make the www subdomain your default domain to avoid redirect loops.

Verification can take up to 48 hours, though it usually clears within a few hours, and OVHcloud zone edits need up to 24 hours to propagate fully. We provision SSL certificates through Let's Encrypt and Google Trust Services, so a zone that already carries CAA records needs 0 issue "letsencrypt.org" and 0 issue "pki.goog; cansignhttpexchanges=yes" added, or certificates quietly fail to issue and renew. The CAA record guide has the detail.

Keep OVHcloud email running alongside the site

Webflow hosting doesn't include email, so OVHcloud mailboxes keep working as long as the MX records stay where they are. The A, CNAME, and TXT records above don't touch mail routing, and MX entries live in the same zone editor under their own MX record guide.

The standard OVHcloud MX set for MX Plan, Email Pro, Exchange, and Zimbra looks like this:

Leave those entries alone while you add the Webflow records, because deleting them cuts off mailbox delivery straight away. If you do change them, allow 4 to 24 hours before expecting mail to route correctly again.

Embed OVHcloud Video Center content with Code Embed elements

OVHcloud Video Center generates an iframe snippet for any site, and its own documentation names Webflow among the CMS editors it covers. That snippet drops straight into a Webflow Code Embed element, which accepts up to 50,000 characters of custom code, far more than a video player needs.

To embed a Video Center player:

1. Copy the embed code for the video from OVHcloud Video Center.
2. In Webflow, add an Embed element to the page where the player should sit.
3. Paste the snippet into the element, then publish the site.

Code Embed runs client-side only, so Perl, PHP, Python, and Ruby never execute inside it. A video iframe fits that model without any workaround.

Build with the Webflow and OVHcloud APIs

The API path is for developers and it needs server-side code, so it earns its keep in two situations: when many OVHcloud domains have to be repointed at Webflow sites, and when an OVHcloud-hosted backend needs to read from or react to a Webflow site. Between them, the two APIs cover record changes and content updates on either side.

Four pieces carry most of the load:

• OVHcloud API: The OVHcloud API manages domains and zones through the /domain and /domain/zone routes, authenticated with an application key, application secret, and consumer key.
• OVHcloud service accounts: Service accounts issue an OAuth2 client ID and secret for the same API, which suits code running in production better than a consumer key.
• Webflow Data API: The Data API handles collections and publishing at https://api.webflow.com using Bearer token authentication on every request.
• Webflow webhooks: Webflow webhooks push events such as site_publish and form_submission to any endpoint, servers on OVHcloud infrastructure included.

Events only flow one way on their own. Webflow webhooks can call an OVHcloud-hosted endpoint, but we've found no outbound webhook support in OVHcloud's core API, IAM, Public Cloud, or domain services, so anything that has to fire from the OVHcloud side needs polling or a small middleware service in between.

Automate DNS updates with the OVHcloud API

Agencies repointing dozens of OVHcloud domains at Webflow sites can script the record changes instead of clicking through the Control Panel. Register an API application first to get the application key, application secret, and consumer key. The zone routes only work when the domain actually uses OVHcloud DNS servers, which is the check worth making before writing any code.

To point a domain at Webflow programmatically:

1. Lower the zone's TTL to its lowest available value at least one full TTL period before the change, as the live site migration guide recommends.
2. List existing record IDs with GET /domain/zone/{zoneName}/record.
3. Create the root A record with POST /domain/zone/{zoneName}/record and body fields fieldType: "A", subDomain: "", and target: "198.202.211.1".
4. Update the www CNAME with PUT /domain/zone/{zoneName}/record/{id} and target: "cdn.webflow.com.".
5. Add the verification record with fieldType: "TXT", subDomain: "_webflow", and the one-time-verification value from Site settings.
6. Apply the pending changes with POST /domain/zone/{zoneName}/refresh.

Scope the credential narrowly rather than granting a wildcard. A script that only repoints domains needs GET and POST on /domain/zone/*/record, PUT and DELETE on /domain/zone/*/record/*, and POST on /domain/zone/*/refresh, nothing beyond that. The full request schema sits in the OVHcloud API console.

Sync an OVHcloud-hosted backend with the Webflow CMS

A backend on an OVHcloud VPS or Public Cloud instance can push content into Webflow CMS collections over the Data API. This pattern fits teams keeping product and pricing records in an OVHcloud database while the pages themselves render from collection items.

To run the sync:

1. Send requests to https://api.webflow.com with an Authorization: Bearer <token> header.
2. Find the target collection with GET /v2/sites/{site_id}/collections.
3. Create items with POST /v2/collections/{collection_id}/items, which land in draft state.
4. Update existing items with PATCH /v2/collections/{collection_id}/items, in batches of up to 100 items.
5. Publish with POST /v2/collections/{collection_id}/items/publish and a body of {"itemIds": [...]}.

Publishing is a separate call from creation, so the script decides exactly when synced content appears on the live site.

Trigger OVHcloud-side automation with Webflow webhooks

When the site publishes, a webhook can tell an endpoint on OVHcloud infrastructure to handle the follow-up work, such as purging a cache or starting a deployment.

To wire up the webhook:

1. Register it with POST /v2/sites/{site_id}/webhooks, set triggerType to "site_publish", and set url to your OVHcloud-hosted endpoint.
2. Read siteId, publishedOn, domains, publishedBy, and publishScope from the payload in your handler, as documented in the site publish reference.
3. Verify every request with the x-webflow-timestamp and x-webflow-signature headers, which carry a SHA-256 HMAC, and reject anything older than five minutes.

Twelve other trigger types are available, including form_submission and collection_item_created, and the full event list documents the payload fields for each.

What you can build with the OVHcloud Webflow integration

Once the DNS records land, a Webflow-hosted site runs in front of OVHcloud operations that never had to move.

These are the setups this combination tends to serve:

• A client site on an OVHcloud-registered domain: An agency holding dozens of client domains at OVHcloud adds three records per zone and launches each marketing site on Webflow hosting.
• A business site with French-hosted email: A law firm or accounting practice serves its public site from Webflow while staff mailboxes stay on OVHcloud Email Pro or Hosted Exchange, mail data included.
• A SaaS marketing site backed by EU infrastructure: A product team serves the site from Webflow, points an api subdomain in the same OVHcloud zone at a VPS, and syncs pricing records into collections over the Data API.
• Publish-driven deployment work: A developer routes site_publish events to an OVHcloud endpoint that runs a build job or refreshes assets in S3-compatible Object Storage.

The API path is where this stops being a DNS exercise. If content sync is the reason you're here, start with our guide to the Webflow CMS API.