Zone not found or not accessible on DNS update

Questions
1

Your question

I am using the automatic DNS update for OVH, but when Stalwart tries to update the DNS records, I get error messages: Zone not found or not accessible. How can I solve this?

2

The earlier doc_search result showed this content was in dns-server.md around line 1339-1352. Let me read that section directly.

Let me look for the OVH-specific section in the dns-server reference doc:

The file is very large (5432 lines); let me search for the OVH section specifically.

The file is very large (5432 lines). Let me search the full file differently.

3

The file seems to be very large (5432 lines). Let me search in it differently.

4

That message comes from the OVH zone lookup (a GET on /domain/zone/), and it collapses any underlying 401/403/404 into the same “not found or not accessible” string, so the real cause is upstream, not Stalwart. In order of likelihood: the consumer key isn’t scoped to /domain/zone/* (or was never validated), so OVH returns 403; the wrong region endpoint is configured (ovh-eu vs ovh-ca etc.) so the zone isn’t visible under that API host; or the domain is only registered at OVH but its DNS isn’t hosted as an OVH zone (external nameservers), which gives a 404.

I’d regenerate the OVH token granting GET/POST/PUT/DELETE on /domain/zone/*, confirm the region matches your account, and check the domain is actually using OVH’s nameservers. That’s the same credential setup I described in your other thread, and fixing the scope there should clear this.