Use OVHcloud's API key creation and rights-delegation workflow for the account that owns the DNS zones. Grant the necessary methods on the domain-zone paths, including record reads, updates and zone refresh actions needed by your operation. Limit rights to the intended resources where possible and review expiry before using the key for unattended jobs.

The application identifies your integration; the consumer key authorises its account access. Store the secret values together securely. A key generated for another customer's account cannot be reused merely because both accounts appear in the same administrative workflow.

1. Add a server and choose OVH.
2. Enter Application Key, Application Secret and Consumer Key exactly as issued.
3. Select the matching OVH region: Europe, Canada or US as appropriate for that credential and service.
4. Save and run the connection check. Use an authorised zone to test one temporary TXT change.
5. Wait for the module task, read the provider's records and query the authoritative nameserver before making the connection a production package target.

OVH's provider workflow includes publishing or refreshing zone changes. Inspect the completed task and the provider's active state, then check the registrar's delegation. Repeatedly editing the same value is not a useful substitute for identifying whether the update, refresh or public caching layer is responsible.

Use the credential format exposed by this installed adapter. OVHcloud offers other authentication arrangements, but an OAuth client credential is not interchangeable with the application's three-key configuration. If your organisation requires another method, confirm support before replacing a working connection.

• Rotate a DNS provider credential across all connections that use it
• Check DNS propagation and find the source of an old answer
• Run a controlled DNS provider acceptance check before assigning customer packages
• Connect DNS Made Easy with its paired API credentials

• OVHcloud: First steps with the APIs