Unable to determine base domain for _acme-challenge.ess.eu using names

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: ess.eu

I ran this command: certbot --text --agree-tos --non-interactive certonly --rsa-key-size 4096 -a dns-rfc2136 --cert-name 'sftp.ess.eu' -d 'sftp.ess.eu' --dns-rfc2136-credentials /etc/letsencrypt/dns-rfc2136.ini --dns-rfc2136-propagation-seconds 10 --keep-until-expiring

It produced this output:
Performing the following challenges:
dns-01 challenge for sftp.ess.eu
Cleaning up challenges
Encountered exception during recovery: PluginError: Unable to determine base domain for _acme-challenge.sftp.ess.eu using names: ['_acme-challenge.sftp.ess.eu', 'sftp.ess.eu', 'ess.eu', 'eu'].
Unable to determine base domain for _acme-challenge.sftp.ess.eu using names: ['_acme-challenge.sftp.ess.eu', 'sftp.ess.eu', 'ess.eu', 'eu'].

This command works:
certbot --text --agree-tos --non-interactive certonly --rsa-key-size 4096 -a dns-rfc2136 --cert-name 'wildcard' -d '*.ess.eu' --dns-rfc2136-credentials /etc/letsencrypt/dns-rfc2136.ini --dns-rfc2136-propagation-seconds 10 --keep-until-expiring

My web server is (include version): haproxy 1.8

The operating system my web server runs on is (include version): CentOS 7

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot 1.11.0

I created a new name server and migrated to it recently. After that, dns-01 failed.
The dns-rfc2136.ini config is:

Is there anything wrong with the configuration or my name server?

Please see e.g. sftp.ess.eu | DNSViz Looks like quite the mess for the sftp subdomain.

Also, as far as I know, Certbot and the Certbot RFC 2136 plugin doesn't play nice with CNAMEs. There should be an issue about that on the Certbit Github repo.

Edit: Found the issue: Allow updating domain pointed to by CNAME in DNS plugins · Issue #6566 · certbot/certbot · GitHub


I don't think the CNAME should matter in this case. There is no CNAME on the _acme-challenge label.

Basically, the error says that the nameserver you're sending the update to (new_ns.domain) doesn't think that it's authoritative for ess.eu. If you query your nameserver for the SOA record of that domain, it should come with a response. In your case, it's probably returning REFUSED.

A good response looks like:

$ dig +norecurse +tcp +noall +answer @ns1.esss.se ess.eu soa
ess.eu.                 10800   IN      SOA     ess.eu. registry.esss.se. 2023051712 3600 1800 604800 10800

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.