PowerDNS API zone URL causing 404

[tacerus]

Welcome

• Yes, I'm using a binary release within 2 latest releases.
• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've included all information below (version, config, etc).

What did you expect to see?

I'm using Lego with PowerDNS for about 100 domains on various certificates since a long time already and never encountered any issues - hence I expected no complications with today's certificate request.

What did you see instead?

Today I tried to issue a certificate for two domains, 3gy.pl and mx2.zz0.email. Whilst the challenge for 3gy.pl passed as expected, the program failed with the second one:

[mx2.zz0.email] [mx2.zz0.email] acme: error presenting token: pdns: unexpected HTTP status code 404 when GETing 'http://192.168.0.115:8082/api/v1/servers/localhost/zones/email.'  

It seems to have constructed the API URL based on a DNS zone email., whilst the actual authoritative zone registered in my PowerDNS database is zz0.email. I am unsure why this is - usually it finds the right zone and constructs the correct URL for second and third level requests correctly.

How do you use lego?

Binary

Reproduction steps

/usr/local/bin/lego -a -m="[email protected]" -k ec384 --path /etc/ssl/lego --dns.resolvers 127.0.0.1 --dns pdns -d 3gy.pl -d mx2.zz0.email run --run-hook="/etc/lysergic/certificate-scripts/hooks/3gy.pl.sh"

Version of lego

lego version 4.6.0 openbsd/amd64

Logs

2022/05/10 18:48:17 [INFO] [3gy.pl, mx2.zz0.email] acme: Obtaining bundled SAN certificate
2022/05/10 18:48:18 [INFO] [3gy.pl] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz-v3/100722005897
2022/05/10 18:48:18 [INFO] [mx2.zz0.email] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz-v3/107147900486
2022/05/10 18:48:18 [INFO] [3gy.pl] acme: authorization already valid; skipping challenge
2022/05/10 18:48:18 [INFO] [mx2.zz0.email] acme: Could not find solver for: tls-alpn-01
2022/05/10 18:48:18 [INFO] [mx2.zz0.email] acme: Could not find solver for: http-01
2022/05/10 18:48:18 [INFO] [mx2.zz0.email] acme: use dns-01 solver
2022/05/10 18:48:18 [INFO] [mx2.zz0.email] acme: Preparing to solve DNS-01
2022/05/10 18:48:18 [INFO] [mx2.zz0.email] acme: Cleaning DNS-01 challenge
2022/05/10 18:48:18 [WARN] [mx2.zz0.email] acme: cleaning up failed: pdns: unexpected HTTP status code 404 when GETing 'http://192.168.0.115:8082/api/v1/servers/localhost/zones/email.' 
2022/05/10 18:48:19 [INFO] Skipping deactivating of valid auth: https://acme-v02.api.letsencrypt.org/acme/authz-v3/100722005897
2022/05/10 18:48:19 [INFO] Deactivating auth: https://acme-v02.api.letsencrypt.org/acme/authz-v3/107147900486
2022/05/10 18:48:19 Could not obtain certificates:
        error: one or more domains had a problem:
[mx2.zz0.email] [mx2.zz0.email] acme: error presenting token: pdns: unexpected HTTP status code 404 when GETing 'http://192.168.0.115:8082/api/v1/servers/localhost/zones/email.'

Go environment (if applicable)

n/a

[tacerus]

The same issue occurs with .info zones:

[libcasa.info] [libcasa.info] acme: error presenting token: pdns: unexpected HTTP status code 404 when GETing 'http://192.168.0.115:8082/api/v1/servers/localhost/zones/info.'
[libertacasa.info] [libertacasa.info] acme: error presenting token: pdns: unexpected HTTP status code 404 when GETing 'http://192.168.0.115:8082/api/v1/servers/localhost/zones/info.'
[www.libcasa.info] [www.libcasa.info] acme: error presenting token: pdns: unexpected HTTP status code 404 when GETing 'http://192.168.0.115:8082/api/v1/servers/localhost/zones/info.'