Hi,

I first posted this at LE, but it looks like this more an issue for this issue tracker.

I chose OVH to provide the DNS zone for home.mkrebs.de, while mkrebs.de is hosted at a different DNS provider which does not offer API access.

Now when trying to register a certificate for server.home.mkrebs.de, certbot fails, as it tries to find the zone "mkrebs.de" at OVH, while the zone is named "home.mkrebs.de".

The version of my client is 2.7.0, installed via snapd on Debian Bookworm.

On a SSH shell, I run: sudo certbot certonly --dry-run --dns-ovh -d "server.home.mkrebs.de" --dns-ovh-credentials /etc/letsencrypt/ovh-api.ini

This produces the following output:
Unexpected error determining zone identifier for server.home.mkrebs.de: Domain mkrebs.de not found

From the source code of certbot-dns-ovh, I would assume that the plugin tries server.home.mkrebs.de, home.mkrebs.de, mkrebs.de, but I can't tell for sure. I already can rule out an authorization problem, as the API user has been provided with GET /domain/zone/* privileges (plus PUT/POST/DELETE).

With the ACME plugin, this works fine - but I would love to stick with Certbot.