How long does it take automatic DNS update the records?

Questions
1

Your question

How long does it usually take Stalwart to update OVH’s DNS? I am not certain I have set it up correctly.

I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.

on

2

Good - OVH is confirmed as a supported provider. Here’s a clear answer:

Stalwart’s automatic DNS update to OVH happens near-instantly from Stalwart’s side (it pushes the changes via OVH’s API as soon as you save the domain with automatic DNS management enabled, or when a DnsManagement task runs). The timing you actually observe depends on two things:

  1. Stalwart-side propagation polling - After issuing the update, Stalwart waits for the propagationDelay configured on your DnsServer object, then polls at pollingInterval until the record is visible, up to propagationTimeout. These values are set in your DnsServer configuration (WebUI: Settings > Network > DNS > DNS Providers).

  2. OVH’s own propagation - Once OVH accepts the record, DNS propagation across the internet can still take minutes to hours depending on TTL values.

To verify your setup is working, check the Task log in the WebUI under Management > Tasks (look at both “Scheduled” and “Failed” sections). If the DnsManagement task failed, the failureReason field will tell you exactly what went wrong with the OVH API call. If you don’t see a task at all, make sure the domain’s dnsManagement field is set to Automatic and that it references your OVH DnsServer.

You can also trigger a manual refresh at any time by creating a new DnsManagement task from Management > Tasks > New Task.

Relevant docs: DNS Records - Automatic Management and DNS Providers

This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong.

3

How do I create API key with the proper access at OVH?

4

There isn’t a fixed long interval. When you save a domain with automatic DNS management, Stalwart schedules a task that runs within a few seconds; you can watch it under Management, Tasks (it’ll show as scheduled, then either done or failed with a reason). After the records are written, how fast they’re usable is down to OVH’s own zone refresh plus the record TTL, and Stalwart’s own waiting is governed by the DnsServer object’s propagationDelay, pollingInterval and propagationTimeout, which you can tune. Docs: DNS records | Stalwart and DnsServer | Stalwart.

For the OVH key: create the credentials on OVH’s API token page, pick the region endpoint that matches your account (ovh-eu, ovh-ca, etc.), and make sure the consumer key is granted access to /domain/zone/* for GET, POST, PUT and DELETE. A key scoped only to GET, or to the wrong zone path, is the usual reason updates fail. That’s also almost certainly behind the “Zone not found” you opened separately; see my reply there.